Triple
T18619484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COP15 |
E455110
|
entity |
| Predicate | fastStartFinanceAmount |
P124858
|
FINISHED |
| Object | 30 billion US dollars for 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: 30 billion US dollars for 2010-2012 | Statement: [COP15, fastStartFinanceAmount, 30 billion US dollars for 2010-2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fastStartFinanceAmount Context triple: [COP15, fastStartFinanceAmount, 30 billion US dollars for 2010-2012]
-
A.
agreedFastStartFinance
Indicates that an entity has formally agreed to participate in or support the Fast Start Finance initiative or arrangement.
-
B.
fundingSpeed
Indicates how quickly financial resources are provided or disbursed within a given funding relationship or process.
-
C.
capitalAtBeginning
Indicates that a string or word has a capital (uppercase) letter as its first character.
-
D.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
E.
amountInvolvedApprox
chosen
Indicates that the relationship specifies an approximate value or quantity involved in an action, event, or transaction.
- 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.