Triple
T12833720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boy Wonder |
E306851
|
entity |
| Predicate | associatedWithPersonDeathYear |
P16526
|
FINISHED |
| Object | 1936 |
—
|
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: 1936 | Statement: [The Boy Wonder, associatedWithPersonDeathYear, 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPersonDeathYear Context triple: [The Boy Wonder, associatedWithPersonDeathYear, 1936]
-
A.
yearOfDeath
chosen
Indicates the specific year in which an entity (typically a person or organism) died.
-
B.
diedInSameYearAs
Indicates that two entities each died in the same calendar year.
-
C.
deathYearApproximate
Indicates that the year of an entity’s death is known only approximately rather than as an exact calendar year.
-
D.
associatedWithYearFilm
Indicates a relationship where something (such as an event, award, or record) is linked to or pertains to a specific film released or identified in a given year.
-
E.
associatedWithDeathOf
Indicates a relationship where one entity is connected in some relevant way to the death of another entity, such as by involvement, causation, or contextual association.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:34 p.m.