Triple

T17220490
Position Surface form Disambiguated ID Type / Status
Subject Clain River E417965 entity
Predicate name P16 FINISHED
Object Clain E417965 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: Clain | Statement: [Clain River, name, Clain]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Clain
Context triple: [Clain River, name, Clain]
  • A. Clain River chosen
    The Clain River is a waterway in western France that flows through the city of Poitiers before joining the Vienne River.
  • B. North Hudson
    North Hudson is a densely populated urban region in northern Hudson County, New Jersey, encompassing several closely linked municipalities along the Hudson River waterfront.
  • C. Saconet
    Saconet is an ethnonymic variant referring to the Sakonnet, a Native American people historically associated with the coastal region of what is now southeastern Rhode Island.
  • D. Comasco
    Comasco is a variety of the Lombard language traditionally spoken in and around the city of Como in northern Italy.
  • E. St. Clair
    St. Clair is a township in southwestern Ontario, Canada, situated along the St. Clair River within Lambton County.
  • 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_69d886d779488190b131369541c04e7d completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42ddd52d4819098b51d55e063c8ab completed April 19, 2026, 1:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a016757985881909b5711eb1f206cd7 completed May 11, 2026, 5:21 a.m.
Created at: April 10, 2026, 5:38 a.m.