Triple
T6281404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-European Transport Network |
E140788
|
entity |
| Predicate | objectiveYearCoreNetwork |
P69839
|
FINISHED |
| Object | 2030 |
—
|
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 | Statement: [Trans-European Transport Network, objectiveYearCoreNetwork, 2030]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: objectiveYearCoreNetwork Context triple: [Trans-European Transport Network, objectiveYearCoreNetwork, 2030]
-
A.
planningYear
Indicates the year in which planning or preparation activities for something are scheduled or designated to occur.
-
B.
finalPerformanceYear
Indicates the year in which an entity’s performance or activity is recorded or recognized for the last time.
-
C.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
D.
yearOrchestrated
Indicates the specific year in which a musical work was orchestrated or arranged for orchestra.
-
E.
commissionYear
Indicates the year in which something (such as a work, project, or asset) was formally commissioned or authorized to be created or undertaken.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063dee62881908347283f16dcbe68 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05b37ac1881909e947822490ba4f2 |
completed | March 22, 2026, 9:12 p.m. |
Created at: March 22, 2026, 4:26 p.m.