Triple
T15616851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Cooke |
E375436
|
entity |
| Predicate | nameUsedIn |
P13305
|
FINISHED |
| Object | Cooke (surname) |
E65201
|
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: Cooke (surname) | Statement: [Dennis Cooke, nameUsedIn, Cooke (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cooke (surname) Context triple: [Dennis Cooke, nameUsedIn, Cooke (surname)]
-
A.
Cooke
chosen
Cooke is a surname of English origin, often considered a variant spelling of "Cook."
-
B.
Douglas (surname)
Douglas (surname) is a Scottish family name of Gaelic origin historically associated with a powerful Lowland clan and widely borne in English-speaking countries.
-
C.
Howard (surname)
Howard is an English-language surname of Anglo-Norman and sometimes Irish origin, borne by numerous notable figures in politics, entertainment, and other fields.
-
D.
Smith (surname)
Smith is a common English occupational surname originally denoting a metalworker or blacksmith.
-
E.
Scott (surname)
Scott is a common English and Scottish surname historically associated with people from Scotland or of Scottish descent.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e980b748190b43c0b650bf1e629 |
completed | April 16, 2026, 2:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff56dd1e4c819090bf3cd4425b39b7 |
completed | May 9, 2026, 3:46 p.m. |
Created at: April 10, 2026, 4:13 a.m.