Triple
T8067764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kavanaugh |
E188288
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Kavanagh |
E537037
|
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: Kavanagh | Statement: [Kavanaugh, hasVariant, Kavanagh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kavanagh Context triple: [Kavanaugh, hasVariant, Kavanagh]
-
A.
Kavanagh
chosen
Kavanagh is a surname of Irish origin that appears as a name component in entities such as Praeger-Kavanagh-Waterbury.
-
B.
Mullane
Mullane is a surname of Irish origin, considered a variant of the name Mullen.
-
C.
O'Flanagan
O'Flanagan is an Irish surname, a variant of Flanagan, traditionally associated with Gaelic heritage and families originating in Ireland.
-
D.
O’Donoghue
O’Donoghue is an Irish surname historically associated with several Gaelic families and clans, particularly in County Kerry and surrounding regions.
-
E.
Guilfoyle
Guilfoyle is a surname most prominently associated in contemporary American culture with television personality and political figure Kimberly Guilfoyle.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff8a4fc8190a97fc7111ca7ec4d |
completed | March 31, 2026, 3:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63e587908190980f1f026f4aa153 |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:27 p.m.