Triple
T9392589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Eyes Cody |
E226058
|
entity |
| Predicate | heritageRevelationYear |
P88688
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Iron Eyes Cody, heritageRevelationYear, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageRevelationYear Context triple: [Iron Eyes Cody, heritageRevelationYear, 1996]
-
A.
heritageSince
Indicates that a heritage status, tradition, or cultural legacy has been in effect or recognized starting from a specific point in time.
-
B.
includedInMonumentYear
Indicates that an entity was incorporated into or recognized as part of a monument in a specific year.
-
C.
firstExcavationYear
Indicates the calendar year in which an excavation activity at a given site or object was first carried out.
-
D.
revealedInCentury
Indicates that something became known, disclosed, or publicly revealed during a specified century.
-
E.
excavationYear
Indicates the year in which an excavation activity took place or was conducted.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510fec6481908b51c497744068c8 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:45 p.m.