Triple
T23233770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1315/2013 |
E581230
|
entity |
| Predicate | objectiveYear |
P26643
|
FINISHED |
| Object | 2030 for completion of the core network |
—
|
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: 2030 for completion of the core network | Statement: [Regulation (EU) No 1315/2013, objectiveYear, 2030 for completion of the core network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveYear Context triple: [Regulation (EU) No 1315/2013, objectiveYear, 2030 for completion of the core network]
-
A.
year
Indicates the specific calendar year associated with an entity, event, or fact.
-
B.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
C.
hasGoalYear
chosen
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
D.
objectiveYearComprehensiveNetwork
Indicates that an objective pertains to the year in which a comprehensive network is planned, defined, or evaluated.
-
E.
yearObserved
Indicates the specific calendar year during which the referenced event, condition, or measurement was observed or recorded.
- F. None of above.
Provenance (3 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e7bed88190b914b238c5f49860 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.