Triple
T3488224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Climate Pledge |
E73660
|
entity |
| Predicate | commitmentType |
P445
|
FINISHED |
| Object | voluntary |
—
|
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: voluntary | Statement: [The Climate Pledge, commitmentType, voluntary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commitmentType Context triple: [The Climate Pledge, commitmentType, voluntary]
-
A.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
B.
commitmentGrade
Indicates the level or quality of commitment one entity has made toward another entity or agreed-upon action.
-
C.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
D.
typicalCommitment
Indicates a standard or commonly expected level of obligation or promise that one entity holds toward another or toward performing an action.
-
E.
commitmentTiming
Indicates the point in time or period relative to an event or agreement when a commitment is made, becomes effective, or is expected to be fulfilled.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbb9193688190aa0cbf87a7b99446 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.