Triple
T13620803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patrick J. Durkan |
E325444
|
entity |
| Predicate | nameUsedIn |
P13305
|
FINISHED |
| Object | Durkan (surname) |
E58445
|
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: Durkan (surname) | Statement: [Patrick J. Durkan, nameUsedIn, Durkan (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durkan (surname) Context triple: [Patrick J. Durkan, nameUsedIn, Durkan (surname)]
-
A.
Durrant
Durrant is an English-language surname of Norman origin, borne by various notable individuals in fields such as entertainment, sports, and academia.
-
B.
Durkan
chosen
Durkan is a surname most notably associated with Jenny Durkan, the former mayor of Seattle and an American attorney and politician.
-
C.
Daudley
Daudley is a surname variant historically associated with the English Audley family.
-
D.
Durst
Durst is a surname most prominently associated with the New York real estate–developing Durst family, including figures such as Joseph Durst and his descendants.
-
E.
Dann
Dann is a masculine given name, often used as a variant of "Dan" or "Daniel."
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0b0c9008190836242da2d6a8cbe |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f77fa291f48190a0ee7a228ea303bc |
completed | May 3, 2026, 5:02 p.m. |
Created at: April 9, 2026, 9:50 p.m.