Triple

T12691975
Position Surface form Disambiguated ID Type / Status
Subject City of Byram E303226 entity
Predicate hasOfficialName P66 FINISHED
Object City of Byram E303226 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: City of Byram | Statement: [City of Byram, hasOfficialName, City of Byram]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Byram
Context triple: [City of Byram, hasOfficialName, City of Byram]
  • A. City of Byram chosen
    The City of Byram is a small suburban municipality in central Mississippi, located just south of Jackson.
  • B. City of Rollingwood
    The City of Rollingwood is the municipal government that administers and provides local services to the small, affluent community of Rollingwood in the Austin metropolitan area of Texas.
  • C. Ramsayville
    Ramsayville is the former name of the town now known as Almonte in Ontario, Canada.
  • D. Mebanesville
    Mebanesville was the original name of the city now known as Mebane in North Carolina.
  • E. City of Williams
    The City of Williams is the municipal government authority responsible for administering and providing local services to the community of Williams, California.
  • 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_69d7bdef90d48190b46b88270e780946 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961dbc91c8190bec50797bbd593db completed April 10, 2026, 8:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f671acbd5c8190ad8d1d2f18868369 completed May 2, 2026, 9:50 p.m.
Created at: April 9, 2026, 5:22 p.m.