Triple
T10526027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavan O'Herlihy |
E248307
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gavan |
E60780
|
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: Gavan | Statement: [Gavan O'Herlihy, givenName, Gavan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gavan Context triple: [Gavan O'Herlihy, givenName, Gavan]
-
A.
Gavan
chosen
Gavan is a given name, typically a variant spelling of Gavin, used as a masculine first name in English-speaking contexts.
-
B.
Gillen
Gillen is a small coastal settlement on the Waternish peninsula of the Isle of Skye in Scotland.
-
C.
Dugan
Dugan is a surname and given name of Irish origin, commonly used in English-speaking countries.
-
D.
Gaven
Gaven is a suburb on the Gold Coast in Queensland, Australia, known for its semi-rural character and proximity to major transport routes.
-
E.
Gavan Duffy
Gavan Duffy is the surname of George Gavan Duffy, an Irish politician, lawyer, and signatory of the Anglo-Irish Treaty who later served as a judge.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509f4bbe88190bce7789a56c85671 |
completed | April 7, 2026, 1:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d933fffc4c81908798094f72a06d18 |
completed | April 10, 2026, 5:31 p.m. |
Created at: April 6, 2026, 12:29 p.m.