Triple

T12384028
Position Surface form Disambiguated ID Type / Status
Subject Cusseta, Alabama E295814 entity
Predicate hasOfficialName P66 FINISHED
Object Cusseta, Alabama E295814 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: Cusseta, Alabama | Statement: [Cusseta, Alabama, hasOfficialName, Cusseta, Alabama]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cusseta, Alabama
Context triple: [Cusseta, Alabama, hasOfficialName, Cusseta, Alabama]
  • A. Cusseta, Alabama chosen
    Cusseta, Alabama is a small rural town in eastern Alabama known for its quiet community within Chambers County.
  • B. Atmore, Alabama
    Atmore, Alabama is a small city in Escambia County near the Florida state line, known historically for its railroad roots and proximity to several state and federal correctional facilities.
  • C. Lanett, Alabama
    Lanett, Alabama is a small city in eastern Alabama near the Georgia border, historically tied to the textile industry and the Chattahoochee River region.
  • D. Webb, Alabama
    Webb, Alabama is a small town located in southeastern Alabama within the Dothan metropolitan area.
  • E. Opelika
    Opelika is a city in eastern Alabama known for its proximity to Auburn and its role as a regional center for industry and commerce.
  • 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_69d6ad9e653c8190b1473c860ee53dae completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d93fbc3f608190b0ee3c4f304a94db completed April 10, 2026, 6:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6eac3ebd08190beb13fa00331f27b completed May 3, 2026, 6:27 a.m.
Created at: April 8, 2026, 9:54 p.m.