Triple

T12967392
Position Surface form Disambiguated ID Type / Status
Subject Lawson, Missouri E321297 entity
Predicate hasOfficialName P66 FINISHED
Object Lawson, Missouri E321297 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: Lawson, Missouri | Statement: [Lawson, Missouri, hasOfficialName, Lawson, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lawson, Missouri
Context triple: [Lawson, Missouri, hasOfficialName, Lawson, Missouri]
  • A. Lawson, Missouri chosen
    Lawson, Missouri is a small Midwestern city that lies within the Kansas City metropolitan area and spans parts of Ray and Clay counties.
  • B. Lohman, Missouri
    Lohman, Missouri is a small town in Cole County that forms part of the Jefferson City metropolitan area in central Missouri.
  • C. Lockwood, Missouri
    Lockwood, Missouri is a small rural city in southwestern Missouri known for its agricultural community and small-town character.
  • D. Lemay, Missouri
    Lemay, Missouri is an unincorporated suburban community in south St. Louis County known for its proximity to the historic Jefferson Barracks military post and the Mississippi River.
  • E. Levasy, Missouri
    Levasy, Missouri is a small rural city located in eastern Jackson County within the Kansas City metropolitan area.
  • 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_69d80763bd6c819094437da5b20b01d2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97e3f702481908f0f90f4f12d3f4d completed April 10, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f75469a3f08190a7e417872147b455 completed May 3, 2026, 1:58 p.m.
Created at: April 9, 2026, 8:30 p.m.