Triple
T15550085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John McSherry |
E370719
|
entity |
| Predicate | positionAtTimeOfDeath |
P105035
|
FINISHED |
| Object | home plate umpire |
—
|
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: home plate umpire | Statement: [John McSherry, positionAtTimeOfDeath, home plate umpire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionAtTimeOfDeath Context triple: [John McSherry, positionAtTimeOfDeath, home plate umpire]
-
A.
positionOnDeath
chosen
Indicates the role, title, or position an entity held at the time of its death.
-
B.
timeOfDeath
Indicates the specific time at which an entity (typically a person or organism) died.
-
C.
bodyLocationAfterDeath
Indicates the location or position of an entity’s body after its death.
-
D.
diesAtMomentOf
Indicates that one entity ceases to live precisely at the specific moment or time point associated with another entity or event.
-
E.
positionOnDeathPenalty
Indicates a stance or viewpoint an entity holds regarding the use, legality, or morality of the death penalty.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a93121881909d88ca55a39252ac |
completed | April 16, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:08 a.m.