Triple
T19139411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | statue of Johnny Bench |
E468515
|
entity |
| Predicate | hasSubjectHonor |
P36838
|
FINISHED |
| Object | National Baseball Hall of Fame inductee |
—
|
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: National Baseball Hall of Fame inductee | Statement: [statue of Johnny Bench, hasSubjectHonor, National Baseball Hall of Fame inductee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubjectHonor Context triple: [statue of Johnny Bench, hasSubjectHonor, National Baseball Hall of Fame inductee]
-
A.
hasCodeOfHonor
Indicates that an entity adheres to a personal or shared ethical code that guides its behavior and decisions.
-
B.
hasNotableHonor
chosen
Indicates that an entity has received a significant award, title, or formal recognition of distinction.
-
C.
hasHonorificSubject
Indicates that a subject is associated with a formal title or honorific used to address or refer to them.
-
D.
isHonor
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
E.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
- 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_69d8dd0796a48190b34ce4cd9d3f3be5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e3ef883c8190829138a560f2a3dc |
completed | April 20, 2026, 8:29 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.