Triple
T13296325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Douglas, 1st Duke of Queensberry |
E316692
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Douglas |
E327242
|
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: Douglas | Statement: [William Douglas, 1st Duke of Queensberry, familyName, Douglas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Douglas Context triple: [William Douglas, 1st Duke of Queensberry, familyName, Douglas]
-
A.
Douglas
Douglas is a masculine given name of Scottish origin that has been widely used in English-speaking countries.
-
B.
Douglas
Douglas is a town in South Lanarkshire, Scotland, historically known for its association with the powerful Douglas family and its medieval castle.
-
C.
Douglas
Douglas is a community area on the South Side of Chicago, Illinois, known for its historic residential neighborhoods and proximity to the city’s lakefront.
-
D.
Douglas
chosen
Douglas is a historic Scottish noble house that played a major role in the political and military history of medieval and early modern Scotland.
-
E.
Douglas
Douglas is a suburban area of Cork, Ireland, known as a residential and commercial hub just southeast of Cork city centre.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99079c8508190b6208db9affcbc0e |
completed | April 11, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716dad3648190bf360955fbdfb2f0 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:28 p.m.