Triple
T6610044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Leary |
E149213
|
entity |
| Predicate | hasPatronymicForm |
P7966
|
FINISHED |
| Object | Ó Laoghaire |
E602687
|
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: Ó Laoghaire | Statement: [O'Leary, hasPatronymicForm, Ó Laoghaire]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ó Laoghaire Context triple: [O'Leary, hasPatronymicForm, Ó Laoghaire]
-
A.
Ó Nualláin
Ó Nualláin is an Irish-language surname that corresponds to the anglicized family name Nolan.
-
B.
Ó Donnabháin
Ó Donnabháin is an Irish Gaelic surname from which the anglicized family name Donovan is derived.
-
C.
Suilleabháin
Suilleabháin is an Irish surname, traditionally anglicized as Sullivan, with roots in Gaelic heritage and history.
-
D.
Fingal
Fingal is a county in eastern Ireland, north of Dublin, known for its coastal towns, historical sites, and rapidly growing suburban communities.
-
E.
Ó Laoire
chosen
Ó Laoire is an Irish Gaelic surname that represents the original form from which the anglicized name O'Leary is derived.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6af3301dc819082d427675c36aaa6 |
completed | March 27, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7006b27f08190b06427480689bdbd |
completed | March 27, 2026, 10:10 p.m. |
Created at: March 27, 2026, 1:57 p.m.