Triple
T13053228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azores Time |
E327497
|
entity |
| Predicate | followsEuropeanDSTRules |
P108476
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: true | Statement: [Azores Time, followsEuropeanDSTRules, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsEuropeanDSTRules Context triple: [Azores Time, followsEuropeanDSTRules, true]
-
A.
usesEuropeanUnionDSTRules
Indicates that the action or process is governed by, or conforms to, the European Union’s Digital Services Act (DSA) rules and requirements.
-
B.
followsDSTRulesOf
Indicates that one entity adheres to or complies with the decision support tool (DST) rules defined or used by another entity.
-
C.
isProEuropean
Indicates support for European integration, institutions, or policies, or a generally favorable stance toward the European Union.
-
D.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
-
E.
followsDSTRule
Indicates that one entity adheres to or complies with a specified DSTRule in its behavior or processing.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
| PDg | Predicate description generation | batch_69d98a9577d081908ddef9ea77e408e2 |
completed | April 10, 2026, 11:41 p.m. |
Created at: April 9, 2026, 8:58 p.m.