Triple

T17606503
Position Surface form Disambiguated ID Type / Status
Subject Auto-Ordnance Bridgeport E428845 entity
Predicate locatedIn P40 FINISHED
Object Bridgeport, Connecticut 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: Bridgeport, Connecticut | Statement: [Auto-Ordnance Bridgeport, locatedIn, Bridgeport, Connecticut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bridgeport, Connecticut
Context triple: [Auto-Ordnance Bridgeport, locatedIn, Bridgeport, Connecticut]
  • A. Bridgeport
    Bridgeport is a small city in Wise County, Texas, known for its historic downtown and proximity to Lake Bridgeport.
  • B. Bridgeport
    Bridgeport is a historic, working-class neighborhood on Chicago’s South Side known for its strong ethnic communities and proximity to the city’s major sports venues.
  • C. Bridgeport chosen
    Bridgeport is a coastal industrial city in southwestern Connecticut known for its historic manufacturing base and diverse urban population.
  • D. Bridgeport
    Bridgeport is a small rural city in western Nebraska that serves as a local agricultural and community hub.
  • E. Bridgeport
    Bridgeport is a mixed residential and commercial neighborhood in Richmond, British Columbia, known for its proximity to major transportation routes and the Fraser River.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46c4ccef08190aeaa88670364bd74 completed April 19, 2026, 5:46 a.m.
Created at: April 10, 2026, 5:51 a.m.