Triple

T1975490
Position Surface form Disambiguated ID Type / Status
Subject Gloucester Lock E42900 entity
Predicate locatedIn P40 FINISHED
Object Gloucester E21326 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: Gloucester | Statement: [Gloucester Lock, locatedIn, Gloucester]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gloucester
Context triple: [Gloucester Lock, locatedIn, Gloucester]
  • A. Gloucester
    Gloucester is a historic coastal city in northeastern Massachusetts known for its long-standing fishing industry and maritime heritage.
  • B. Gloucester chosen
    Gloucester is a historic cathedral city and port in southwest England, known for its medieval architecture and role as the county town of Gloucestershire.
  • C. Bristol
    Bristol is a historic port city in southwest England known for its maritime heritage, vibrant cultural scene, and distinctive Georgian and Victorian architecture.
  • D. Coventry
    Coventry is a historic city in England, best known for its medieval cathedral destroyed in World War II and its symbolic postwar reconciliation efforts.
  • E. Swindon
    Swindon is a large town in Wiltshire, England, known as a major commercial and commuter hub in the southwest with strong railway and industrial heritage.
  • 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_69a8871289048190b00b0d7744b7b2b1 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb3f835108190b0709ccf3a487a96 completed March 7, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae2702954c8190b95de378e263574a completed March 9, 2026, 1:48 a.m.
Created at: March 4, 2026, 7:36 p.m.