Triple
T29809026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Earth |
E756907
|
entity |
| Predicate | usedCarbonOffsetting |
P168785
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Live Earth, usedCarbonOffsetting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCarbonOffsetting Context triple: [Live Earth, usedCarbonOffsetting, true]
-
A.
hasCarbonFootprintCategory
Indicates that an entity is associated with a specific classification of its carbon footprint level or impact.
-
B.
environmentalImpactGoal
Indicates a goal or target set to influence, reduce, or manage the environmental impact associated with an entity or activity.
-
C.
environmentalCommitment
Indicates a relationship where an entity demonstrates dedication to protecting or improving the environment through its policies, actions, or practices.
-
D.
hasEnvironmentalImpactOn
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
-
E.
CDP
Indicates a relationship where an entity is associated with or participates in a specific CDP (such as a program, platform, or process) in a defined role or capacity.
- F. None of above. chosen
Provenance (4 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67805551c81909e016ae9e3031076 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 5:22 p.m.