Triple

T19164614
Position Surface form Disambiguated ID Type / Status
Subject California State Route 168 E469144 entity
Predicate serves P98 FINISHED
Object Clovis E113425 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: Clovis | Statement: [California State Route 168, serves, Clovis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clovis
Context triple: [California State Route 168, serves, Clovis]
  • A. Clovis
    Clovis is a small city in eastern New Mexico known as a regional hub for agriculture, rail transport, and nearby Cannon Air Force Base.
  • B. Clovis
    Clovis is a masculine given name of Germanic origin, historically associated with early Frankish kings and related to names like Louis and Ludwig.
  • C. Clovis chosen
    Clovis is a city in Fresno County, California, known as a gateway to the Sierra Nevada and for its historic Old Town district.
  • D. Clovis
    Clovis is a prehistoric Native American culture known for its distinctive fluted stone spear points and for representing some of the earliest widely accepted human inhabitants of North America.
  • E. Clovis II
    Clovis II was a 7th-century Merovingian king of Neustria and Burgundy, known for his weak rule under the dominance of powerful nobles and mayors of the palace.
  • 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_69d8dd09d5a081909ae43c286651ae5a completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5f15e2720819084b1707497db26a2 completed April 20, 2026, 9:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a06f25ef2208190842d2b29bee2c8ce completed May 15, 2026, 10:15 a.m.
Created at: April 10, 2026, 12:06 p.m.