Triple
T18619668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REDD+ |
E455113
|
entity |
| Predicate | targetsActivity |
P35065
|
FINISHED |
| Object | reducing emissions from deforestation |
—
|
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: reducing emissions from deforestation | Statement: [REDD+, targetsActivity, reducing emissions from deforestation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsActivity Context triple: [REDD+, targetsActivity, reducing emissions from deforestation]
-
A.
targetedActivity
chosen
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
B.
targetUserActivity
Indicates that a specific user is the intended recipient or focus of a particular activity or action.
-
C.
associatedActivity
Indicates that one entity is linked to, involved in, or characterized by a particular activity or set of activities.
-
D.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
E.
coordinatesActivitiesOf
Indicates that one entity organizes, aligns, or manages the activities of another entity or group of entities so they work together effectively.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f00889c8190931f8d3fbabd531b |
completed | April 19, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.