Triple
T16082065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Tigers Hall of Fame |
E390133
|
entity |
| Predicate | includesHonoreesType |
P58949
|
FINISHED |
| Object | players |
—
|
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: players | Statement: [Detroit Tigers Hall of Fame, includesHonoreesType, players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHonoreesType Context triple: [Detroit Tigers Hall of Fame, includesHonoreesType, players]
-
A.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
B.
honoreeHallOfFame
Indicates that an entity is recognized as an inductee or honoree in a particular Hall of Fame.
-
C.
typicalHonoree
chosen
Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with another entity.
-
D.
honoredPerson
Indicates that a person is the recipient of honor, recognition, or special distinction from another party or in a particular context.
-
E.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.