Triple

T9070989
Position Surface form Disambiguated ID Type / Status
Subject Montagu Douglas Scott family E217364 entity
Predicate familyNameComponent 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: [Montagu Douglas Scott family, familyNameComponent, Douglas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Douglas
Context triple: [Montagu Douglas Scott family, familyNameComponent, 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 small lakeside city in Allegan County, Michigan, known for its arts community and proximity to Lake Michigan beaches.
  • C. Douglas
    Douglas is a small community located on Douglas Island across from downtown Juneau in southeastern Alaska.
  • D. Douglas
    Douglas is a narrow-gauge steam locomotive that operates on the historic Talyllyn Railway in Wales.
  • E. 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.
  • 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_69ca83d5a7f48190b16c1e59bd43ede0 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc955ec5c0819089bb42448edf391e completed April 1, 2026, 3:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffde470388190ae88a96654404410 completed April 3, 2026, 5:50 p.m.
Created at: March 30, 2026, 7:12 p.m.