Triple

T21099956
Position Surface form Disambiguated ID Type / Status
Subject Lindford E519872 entity
Predicate nearbySettlement P350 FINISHED
Object Bordon 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: Bordon | Statement: [Lindford, nearbySettlement, Bordon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bordon
Context triple: [Lindford, nearbySettlement, Bordon]
  • A. Bordon chosen
    Bordon is a town in East Hampshire, England, historically known for its large army camp and military training facilities.
  • B. Loano
    Loano is a coastal town and popular tourist resort on the Italian Riviera in the Liguria region of northwestern Italy.
  • C. Bengower
    Bengower is a prominent mountain peak in County Galway, Ireland, forming part of the rugged Twelve Bens range in Connemara.
  • D. Bridgeland
    Bridgeland is a large, master-planned residential community in Cypress, Texas, known for its extensive amenities, green spaces, and family-oriented neighborhoods.
  • E. Basford
    Basford is a suburban area of Nottingham, England, known for its mix of residential neighborhoods and light industry.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b508d8dc81909be940dafe36c8f7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e71b5cef408190821d345417b77116 completed April 21, 2026, 6:38 a.m.
Created at: April 16, 2026, 2:53 p.m.