Triple

T27460547
Position Surface form Disambiguated ID Type / Status
Subject Windsor–Detroit border E692724 entity
Predicate hasLanguageOnUSSide P103974 FINISHED
Object English LITERAL 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: English | Statement: [Windsor–Detroit border, hasLanguageOnUSSide, English]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnUSSide
Context triple: [Windsor–Detroit border, hasLanguageOnUSSide, English]
  • A. hasLanguageOfSide chosen
    Indicates that an entity uses or is associated with a particular language on a specific side or aspect (e.g., one side of a bilingual object or interface).
  • B. hasLanguageOn
    Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
  • C. hasLanguageOfSurroundingCountries
    Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
  • D. hasLanguageOfMission
    Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
  • E. hasLanguageOnCanadianSide
    Indicates that a specified language is used or present on the Canadian side of a border, region, or context.
  • F. None of above.

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_69ef5207903881909427745cda05d27a completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f7b5ccbda481908fe1945c35e36ce8 completed May 3, 2026, 8:53 p.m.
PD Predicate disambiguation batch_69f7b4c06f5881908f0b98cad6796478 completed May 3, 2026, 8:49 p.m.
Created at: April 27, 2026, 12:50 p.m.