Triple
T923997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 UN Climate Summit |
E19942
|
entity |
| Predicate | aimedToSupport |
P1853
|
FINISHED |
| Object | UNFCCC negotiations |
—
|
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: UNFCCC negotiations | Statement: [2014 UN Climate Summit, aimedToSupport, UNFCCC negotiations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimedToSupport Context triple: [2014 UN Climate Summit, aimedToSupport, UNFCCC negotiations]
-
A.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
B.
supporterOf
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
-
C.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
D.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
-
E.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3296f50819087f809fbe90b139e |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b295b02481908e5f53bfcb83cc94 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.