Triple
T2692935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Durkan |
E58445
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Joseph Durkan
Joseph Durkan is a notable individual who shares the Durkan surname, recognized enough to be specifically identified among its bearers.
|
E321374
|
NE FINISHED |
How this triple was built (4 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: Joseph Durkan | Statement: [Durkan, hasNotableBearer, Joseph Durkan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joseph Durkan Context triple: [Durkan, hasNotableBearer, Joseph Durkan]
-
A.
John Durkan
John Durkan is a notable individual distinguished enough in his field or public life to be specifically recognized as a bearer of the surname Durkan.
-
B.
Paul Durkan
Paul Durkan is an Irish poet known for his darkly comic, conversational verse that often explores family, politics, and contemporary Irish life.
-
C.
Michael Durkan
Michael Durkan is a notable individual who shares the Durkan surname, recognized as a distinguished bearer of that family name.
-
D.
James Durkan
James Durkan is a notable individual recognized as a prominent bearer of the Durkan surname.
-
E.
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.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Joseph Durkan Triple: [Durkan, hasNotableBearer, Joseph Durkan]
Generated description
Joseph Durkan is a notable individual who shares the Durkan surname, recognized enough to be specifically identified among its bearers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Joseph Durkan Target entity description: Joseph Durkan is a notable individual who shares the Durkan surname, recognized enough to be specifically identified among its bearers.
-
A.
John Durkan
John Durkan is a notable individual distinguished enough in his field or public life to be specifically recognized as a bearer of the surname Durkan.
-
B.
Paul Durkan
Paul Durkan is an Irish poet known for his darkly comic, conversational verse that often explores family, politics, and contemporary Irish life.
-
C.
Michael Durkan
Michael Durkan is a notable individual who shares the Durkan surname, recognized as a distinguished bearer of that family name.
-
D.
James Durkan
James Durkan is a notable individual recognized as a prominent bearer of the Durkan surname.
-
E.
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.
- F. None of above. chosen
Provenance (5 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0dd97c81909a60cf200f57c087 |
completed | March 7, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1de7ea6b48190a992ef2c4b3d7c42 |
completed | March 11, 2026, 9:28 p.m. |
| NEDg | Description generation | batch_69b1e4e2ccb08190932caf81646db1fe |
completed | March 11, 2026, 9:55 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b1e536247c8190a2b3b0fc2d1095e5 |
completed | March 11, 2026, 9:57 p.m. |
Created at: March 6, 2026, 9:54 p.m.