Triple
T8204604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAR |
E191657
|
entity |
| Predicate | identifiedCause |
P708
|
FINISHED |
| Object | anthropogenic greenhouse gas emissions |
—
|
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: anthropogenic greenhouse gas emissions | Statement: [FAR, identifiedCause, anthropogenic greenhouse gas emissions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedCause Context triple: [FAR, identifiedCause, anthropogenic greenhouse gas emissions]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
C.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
D.
causeSupported
Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
-
E.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7268e2dc8190b630ea2bb75d0474 |
completed | March 31, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.