Triple
T12837790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Durkan |
E306962
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | James Durkan |
E306962
|
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: James Durkan | Statement: [James Durkan, name, James Durkan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: James Durkan Context triple: [James Durkan, name, James Durkan]
-
A.
James Durkan
chosen
James Durkan is a notable individual recognized as a prominent bearer of the Durkan surname.
-
B.
David Durkan
David Durkan is a person notable enough to be recognized as a bearer of the surname Durkan, though specific widely known public details about him are not clearly established.
-
C.
Joseph Durkan
Joseph Durkan is a notable individual who shares the Durkan surname, recognized enough to be specifically identified among its bearers.
-
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.
Michael Durkan
Michael Durkan is a notable individual who shares the Durkan surname, recognized as a distinguished bearer of that family 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff015f4819090070a01f3938acc |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6af4f56108190b75dbf9bb144e94a |
completed | May 3, 2026, 2:13 a.m. |
Created at: April 9, 2026, 5:35 p.m.