Triple
T10848878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | multiannual financial framework of the European Union |
E256087
|
entity |
| Predicate | timeHorizonMinimum |
P38657
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [multiannual financial framework of the European Union, timeHorizonMinimum, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeHorizonMinimum Context triple: [multiannual financial framework of the European Union, timeHorizonMinimum, 5 years]
-
A.
timeHorizonOfLoans
Indicates the length of time over which loans are scheduled to be outstanding or repaid.
-
B.
agingTimeMinimum
Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
-
C.
goalHorizon
chosen
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodAfter
Indicates that one time period occurs entirely later than another time period in a temporal sequence.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75114ca988190a0e730131adb2df0 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.