Triple
T18619534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 Accord |
E455111
|
entity |
| Predicate | fastStartFinancePeriod |
P128873
|
FINISHED |
| Object | 2010–2012 |
—
|
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: 2010–2012 | Statement: [COP15 Accord, fastStartFinancePeriod, 2010–2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastStartFinancePeriod Context triple: [COP15 Accord, fastStartFinancePeriod, 2010–2012]
-
A.
focusPeriodStart
Indicates the point in time at which a specified focus period or interval begins.
-
B.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
-
C.
fiscalYearStartInfluence
Indicates how the start date or structure of a fiscal year affects or shapes a related process, condition, or outcome.
-
D.
programStartPeriod
chosen
Indicates the time interval during which a program is initially scheduled to begin or become active.
-
E.
agreedFastStartFinance
Indicates that an entity has formally agreed to participate in or support the Fast Start Finance initiative or arrangement.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d07dc288190bb3b8b5ab06518da |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.