Triple
T18950147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) No 1288/2013 |
E463624
|
entity |
| Predicate | programmePeriodStart |
P89186
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Regulation (EU) No 1288/2013, programmePeriodStart, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmePeriodStart Context triple: [Regulation (EU) No 1288/2013, programmePeriodStart, 2014]
-
A.
programmeStart
chosen
Indicates the point in time or event at which a programme begins or is initiated.
-
B.
successorProgrammeStart
Indicates that the start time or date of a programme directly follows or succeeds that of another programme in a sequence.
-
C.
recordedInPeriodStart
Indicates that an event or record began or was first documented at the start of a specified time period.
-
D.
narratedPeriodStart
Indicates the point in time at which the narrated or described period begins.
-
E.
programStartPeriod
Indicates the time interval during which a program is initially scheduled to begin or become active.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d542b238819089ccd2df279a2f7f |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon