Triple
T9726650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roger Byrne |
E235630
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Byrne |
E507741
|
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: Byrne | Statement: [Roger Byrne, familyName, Byrne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byrne Context triple: [Roger Byrne, familyName, Byrne]
-
A.
Byrne
chosen
Byrne is a common Irish surname borne by numerous notable figures in fields such as literature, entertainment, and politics.
-
B.
Byrnes
Byrnes is a surname of Irish origin borne by various notable individuals, including American politician and statesman James F. Byrnes.
-
C.
O'Byrne
O'Byrne is an Irish surname, a variant of Byrne, traditionally associated with Gaelic families from County Wicklow and surrounding regions.
-
D.
Byrns
Byrns is a surname most notably associated with Joseph W. Byrns, a prominent early 20th-century American politician and Speaker of the U.S. House of Representatives.
-
E.
Browne
Browne is the surname of Lord Browne of Madingley, the prominent British businessman and former chief executive of BP.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e798c348190885b79d7dffc9d8d |
completed | April 1, 2026, 10:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fadc2948190b405fb7f249b82aa |
completed | April 4, 2026, 11:33 p.m. |
Created at: March 30, 2026, 8:21 p.m.