Triple

T15845541
Position Surface form Disambiguated ID Type / Status
Subject Rochestown E384202 entity
Predicate adjacentTo P224 FINISHED
Object Douglas E379389 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: [Rochestown, adjacentTo, Douglas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Douglas
Context triple: [Rochestown, adjacentTo, Douglas]
  • A. Douglas
    Douglas is a town in South Lanarkshire, Scotland, historically known for its association with the powerful Douglas family and its medieval castle.
  • B. 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.
  • C. 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.
  • D. Douglas chosen
    Douglas is a suburban area of Cork, Ireland, known as a residential and commercial hub just southeast of Cork city centre.
  • E. Douglas
    Douglas is a small rural community located within the township of Bonnechere Valley in eastern Ontario, Canada.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e14ca636048190bc89cd8b4efa89e9 completed April 16, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa143dcb48190951648edeae6542d completed May 9, 2026, 9:04 p.m.
Created at: April 10, 2026, 4:50 a.m.