Triple
T16715272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Killer |
E406207
|
entity |
| Predicate | bearerHallOfFameInductionYear |
P7533
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [The Killer, bearerHallOfFameInductionYear, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerHallOfFameInductionYear Context triple: [The Killer, bearerHallOfFameInductionYear, 1986]
-
A.
teamHallOfFameInduction
Indicates that an individual has been formally inducted into a specific team’s Hall of Fame.
-
B.
hallOfFameInductionYear
chosen
Indicates the year in which an entity was formally inducted into a hall of fame.
-
C.
hasInducteesFrom
Indicates that an entity includes or contains individuals who have been formally inducted from another specified group, source, or category.
-
D.
hasInductees
Indicates that an entity has one or more individuals formally inducted or admitted into it, such as into a group, hall, or organization.
-
E.
inductedInto
Indicates that an entity has been formally admitted or entered into a group, organization, hall of fame, or similar body, typically as an honor or official recognition.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38654ee4c8190abf36c29d6610a96 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.