Triple
T12970272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Durkan |
E321374
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Joseph Durkan |
E321374
|
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: Joseph Durkan | Statement: [Joseph Durkan, name, Joseph Durkan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joseph Durkan Context triple: [Joseph Durkan, name, Joseph Durkan]
-
A.
Joseph Durkan
chosen
Joseph Durkan is a notable individual who shares the Durkan surname, recognized enough to be specifically identified among its bearers.
-
B.
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.
-
C.
Paul Durkan
Paul Durkan is an Irish poet known for his darkly comic, conversational verse that often explores family, politics, and contemporary Irish life.
-
D.
Michael Durkan
Michael Durkan is a notable individual who shares the Durkan surname, recognized as a distinguished bearer of that family name.
-
E.
James Durkan
James Durkan is a notable individual recognized as a prominent bearer of the Durkan surname.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e407e5081909424fc0c22483c28 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8e6b31c8190b09276003f284f25 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:34 p.m.