Triple
T4578954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanessa Nakate |
E101806
|
entity |
| Predicate | hasCalledFor |
P2350
|
FINISHED |
| Object | greater climate ambition from industrialized countries |
—
|
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: greater climate ambition from industrialized countries | Statement: [Vanessa Nakate, hasCalledFor, greater climate ambition from industrialized countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCalledFor Context triple: [Vanessa Nakate, hasCalledFor, greater climate ambition from industrialized countries]
-
A.
hasCalledProgram
Indicates that one program has invoked or executed another program.
-
B.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication to another entity.
-
C.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
callsFor
chosen
Indicates that one entity requires, demands, or requests the occurrence of another action, condition, or entity.
-
E.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd58e3e028819083c4662deb9f3c03 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.