Triple
T12646485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Durkan |
E302036
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Brian Durkan |
E302036
|
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: Brian Durkan | Statement: [Brian Durkan, name, Brian Durkan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brian Durkan Context triple: [Brian Durkan, name, Brian Durkan]
-
A.
Brian Durkan
chosen
Brian Durkan is an individual notable enough to be specifically cited as a bearer of the surname Durkan, though detailed public information about his life or achievements is limited.
-
B.
James Durkan
James Durkan is a notable individual recognized as a prominent bearer of the Durkan surname.
-
C.
Stephen Durkan
Stephen Durkan is a contemporary Scottish poet and writer known for his sharp, socially observant verse and contributions to the UK literary scene.
-
D.
Thomas Durkan
Thomas Durkan is a relatively obscure individual whose primary current notability appears to derive from being listed as a namesake of the surname Durkan.
-
E.
Peter Durkan
Peter Durkan is a notable individual associated with the Durkan name, recognized for his public prominence or professional achievements.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9614cefdc81908cfc4a4d04aa6eda |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6719a45d881908dd895836a225781 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:17 p.m.