Triple
T13245902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Durkan |
E315401
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Durkan |
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 | Statement: [Thomas Durkan, hasFamilyName, Durkan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Durkan Context triple: [Thomas Durkan, hasFamilyName, Durkan]
-
A.
Durkan
chosen
Durkan is a surname most notably associated with Jenny Durkan, the former mayor of Seattle and an American attorney and politician.
-
B.
Dugan
Dugan is a surname and given name of Irish origin, commonly used in English-speaking countries.
-
C.
Dugal
Dugal is a masculine given name of Scottish origin, closely related to and often considered a variant of the name Dugald.
-
D.
Durnan
Durnan is a surname most notably associated with Bill Durnan, a Hall of Fame Canadian ice hockey goaltender who starred for the Montreal Canadiens in the 1940s.
-
E.
Daymian
Daymian is a masculine given name, typically considered a modern spelling variant of Damian.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d5c09f88190bb1566a6d8c073a6 |
completed | April 10, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff3600388190a7f61370f54d5e63 |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:23 p.m.