Triple

T14887818
Position Surface form Disambiguated ID Type / Status
Subject Michael John Douglas E359673 entity
Predicate familyName P18 FINISHED
Object Douglas E80 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: [Michael John Douglas, familyName, Douglas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Douglas
Context triple: [Michael John Douglas, familyName, Douglas]
  • A. Douglas chosen
    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
    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_69d827980cbc8190a0c569ae3940a1d9 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69ded5f5b1c88190815f3585770cb135 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b5f22c08190a9530cbd78cfc801 completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 2:08 a.m.