Triple
T10162608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bali Action Plan |
E233925
|
entity |
| Predicate | negotiationDeadline |
P79339
|
FINISHED |
| Object | COP15 in 2009 |
—
|
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: COP15 in 2009 | Statement: [Bali Action Plan, negotiationDeadline, COP15 in 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: negotiationDeadline Context triple: [Bali Action Plan, negotiationDeadline, COP15 in 2009]
-
A.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
B.
notificationDeadline
chosen
Indicates the time or date by which a required notification must be sent or received.
-
C.
negotiatedAfter
Indicates that one negotiation event occurred later in time than another referenced event or negotiation.
-
D.
negotiationPhase
Indicates the specific stage or step currently reached within an ongoing negotiation process between parties.
-
E.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5b5194819095645e9174897b0f |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.