Triple

T17870296
Position Surface form Disambiguated ID Type / Status
Subject Putty E446816 entity
Predicate locatedBetween P1262 FINISHED
Object Windsor NE NERFINISHED

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: Windsor | Statement: [Putty, locatedBetween, Windsor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Windsor
Context triple: [Putty, locatedBetween, Windsor]
  • A. Windsor
    Windsor is a historic English town in Berkshire best known for Windsor Castle, one of the official residences of the British monarch and a major royal and military ceremonial site.
  • B. Windsor
    Windsor is a town in Norfolk, England, served by a station on the Sandringham railway line.
  • C. Windsor
    Windsor is a Canadian city in southwestern Ontario located directly across the Detroit River from Detroit, known for its automotive industry and role as a key border crossing between Canada and the United States.
  • D. Windsor
    Windsor is a village in south-central Wisconsin, United States, located just north of the city of Madison.
  • E. Windsor
    Windsor is a landmark 2013 U.S. Supreme Court case that struck down a key part of the Defense of Marriage Act, advancing federal recognition of same-sex marriages.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

Provenance (2 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_69d8b9f4c22c819093c2680434472894 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49aa24c8481909de38953a88ff615 completed April 19, 2026, 9:04 a.m.
Created at: April 10, 2026, 10:18 a.m.