Triple
T1461587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brennan |
E31523
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Brenan |
E31523
|
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: Brenan | Statement: [Brennan, hasVariant, Brenan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brenan Context triple: [Brennan, hasVariant, Brenan]
-
A.
Bayard
Bayard is a masculine given name most notably associated with civil rights leader Bayard Rustin.
-
B.
Bayard
Bayard is a small town in Grant County, West Virginia, known historically as a coal and timber community in the Appalachian region.
-
C.
Banagher
Banagher is a small Irish town in County Offaly known for its historic bridge over the River Shannon and its traditional boating and angling activities.
-
D.
Bevan
Bevan is a Welsh surname most famously associated with Aneurin Bevan, the Labour politician regarded as the chief architect of the United Kingdom’s National Health Service.
-
E.
Brennan
chosen
Brennan is a surname most prominently associated with William J. Brennan Jr., a long-serving and influential Associate Justice of the United States Supreme Court known for his progressive jurisprudence.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59ecb60819082217b034e18381f |
completed | March 1, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad0e7ab538819090bc3e3ed1bbff64 |
completed | March 8, 2026, 5:51 a.m. |
Created at: March 1, 2026, 8 p.m.