Triple
T5464500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byrns |
E122672
|
entity |
| Predicate | hasVariant |
P455
|
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: [Byrns, hasVariant, Byrne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Byrne Context triple: [Byrns, hasVariant, 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.
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.
-
D.
Browne
Browne is the surname of Lord Browne of Madingley, the prominent British businessman and former chief executive of BP.
-
E.
Browne
Browne is a surname of English and Irish origin commonly used as a family name and occasionally as a middle name.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9204504c81908d638da6f0e271a7 |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf415146988190823ab77b091231a1 |
completed | March 22, 2026, 1:09 a.m. |
Created at: March 20, 2026, 2:08 p.m.