Triple

T17600431
Position Surface form Disambiguated ID Type / Status
Subject D999 road E428684 entity
Predicate connects P390 FINISHED
Object Saint-Affrique NE NERFINISHED

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: Saint-Affrique | Statement: [D999 road, connects, Saint-Affrique]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saint-Affrique
Context triple: [D999 road, connects, Saint-Affrique]
  • A. Saint-Affrique chosen
    Saint-Affrique is a small historic town in southern France known for its rural charm and location in the Aveyron department.
  • B. Tiszanána
    Tiszanána is a village in northern Hungary known for its proximity to the Tisza River and recreational areas around Lake Tisza.
  • C. Kwaluseni
    Kwaluseni is a town in Eswatini known primarily as the main campus site of the University of Eswatini.
  • D. Transkei, South Africa
    Transkei, South Africa was a former bantustan in the southeastern part of the country, historically designated for Xhosa-speaking people during the apartheid era.
  • E. Gǁana
    Gǁana is a Khoe-Kwadi (Khoe) language spoken by a small community of indigenous people in Botswana.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46c4812d48190bf8e899fa8f7fbe4 completed April 19, 2026, 5:46 a.m.
Created at: April 10, 2026, 5:51 a.m.