Triple
T2013996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callaghan |
E43751
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Callahan |
E79981
|
NE 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: Callahan | Statement: [Callaghan, hasVariant, Callahan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Callahan Context triple: [Callaghan, hasVariant, Callahan]
-
A.
Callahan
chosen
Callahan is a surname most notably associated with American singer-songwriter Bill Callahan, known for his introspective and minimalist folk music.
-
B.
Callaghan
Callaghan is a surname of Irish origin borne by numerous notable individuals in politics, sports, and the arts.
-
C.
Haggerty
Haggerty is a surname of Irish origin borne by various notable individuals across fields such as business, politics, and the arts.
-
D.
Cahill
Cahill is a surname of Irish origin borne by numerous notable individuals across sports, politics, and the arts.
-
E.
Coddington
Coddington is an English-origin surname borne by various notable individuals, including early American colonial figures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b42d508190bf2b63132bb2ad77 |
completed | March 7, 2026, 5:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0aeca6388190befe0630d44de109 |
completed | March 8, 2026, 11:49 p.m. |
Created at: March 4, 2026, 7:37 p.m.