Triple
T3913754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sustainable Development Goal 2 |
E87385
|
entity |
| Predicate | hasOverallObjective |
P1415
|
FINISHED |
| Object | end hunger |
—
|
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: end hunger | Statement: [Sustainable Development Goal 2, hasOverallObjective, end hunger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverallObjective Context triple: [Sustainable Development Goal 2, hasOverallObjective, end hunger]
-
A.
hasPrimaryGoal
chosen
Indicates that an entity’s main or most important objective is the specified goal.
-
B.
hasOperationalGoal
Indicates that an entity is associated with a specific objective or target it aims to achieve through its operations or activities.
-
C.
notableObjective
Indicates that an entity has a significant, distinguished, or widely recognized goal, purpose, or target associated with it.
-
D.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
E.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.