Triple
T3913802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sustainable Development Goal 2 |
E87385
|
entity |
| Predicate | hasIconSymbol |
P30078
|
FINISHED |
| Object | bowl with spoon |
—
|
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: bowl with spoon | Statement: [Sustainable Development Goal 2, hasIconSymbol, bowl with spoon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIconSymbol Context triple: [Sustainable Development Goal 2, hasIconSymbol, bowl with spoon]
-
A.
hasIconographicFigure
Indicates that one entity includes, depicts, or is associated with a particular iconographic figure in its visual or symbolic representation.
-
B.
iconOf
chosen
Indicates that one entity serves as a symbolic or representative image or emblem of another entity.
-
C.
hasIconicArea
Indicates that an entity possesses a distinct, widely recognized area or region that is emblematic or characteristic of it.
-
D.
hasColorSymbol
Indicates that one entity is associated with another entity that serves as its representative or symbolic color.
-
E.
hasIconicCharacter
Indicates that something is associated with a character widely recognized as emblematic or highly representative of it.
- 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.