Triple
T22758362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Kelliher |
E562912
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kelliher |
—
|
NE NERFINISHED |
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: Kelliher | Statement: [Bill Kelliher, familyName, Kelliher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kelliher Context triple: [Bill Kelliher, familyName, Kelliher]
-
A.
Kelliher
chosen
Kelliher is an Irish surname, often of Gaelic origin, that appears in various anglicized spellings including Kelleher.
-
B.
Keady
Keady is a surname most prominently associated with Gene Keady, the longtime head coach of the Purdue University men's basketball team.
-
C.
Keady
Keady is a small town and historic settlement in County Armagh, Northern Ireland, known for its traditional linen industry and rural character.
-
D.
Loughery
Loughery is a surname most notably associated with former American professional basketball player and coach Kevin Loughery.
-
E.
Hallglen
Hallglen is a residential area and housing estate within the town of Falkirk in central Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7a8ca481909953dcd6fbcc5fcf |
completed | April 29, 2026, 3:26 a.m. |
Created at: April 17, 2026, 3:25 p.m.