Triple

T16558174
Position Surface form Disambiguated ID Type / Status
Subject Biblical places E402262 entity
Predicate hasExample P1259 FINISHED
Object Antioch E26797 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: Antioch | Statement: [Biblical places, hasExample, Antioch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Antioch
Context triple: [Biblical places, hasExample, Antioch]
  • A. Antioch chosen
    Antioch was an important ancient city in Syria that became a major center of early Christianity and missionary activity.
  • B. Antioch
    Antioch was the former name of the small rural community now known as Louvale in Stewart County, Georgia.
  • C. Antioche
    Antioche is a figure from Greek mythology known primarily as the wife of the hero Eurytus.
  • D. Antioch, California
    Antioch, California is a historic city in the East Bay region of the San Francisco Bay Area known for its suburban communities along the Sacramento–San Joaquin River Delta.
  • E. Antioch, Tennessee
    Antioch, Tennessee is a suburban neighborhood of Nashville known nationally as the site of the 2018 Waffle House shooting stopped by James Shaw Jr.
  • 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_69d8838648088190acf97ef11fc3f61b completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3576bce0c819087ab36f7dec5c394 completed April 18, 2026, 10:05 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0067bcb698819092ede6ba4f8a4a2b completed May 10, 2026, 11:10 a.m.
Created at: April 10, 2026, 5:15 a.m.