Triple

T15186945
Position Surface form Disambiguated ID Type / Status
Subject European route E411 E362899 entity
Predicate passesNear P416 FINISHED
Object Arlon E154217 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: Arlon | Statement: [European route E411, passesNear, Arlon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arlon
Context triple: [European route E411, passesNear, Arlon]
  • A. Arlon chosen
    Arlon is a historic town in southeastern Belgium that serves as the capital of the province of Luxembourg in the Walloon Region.
  • B. Porrentruy
    Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
  • C. Bossey
    Bossey is a small French commune in the Haute-Savoie department of the Auvergne-Rhône-Alpes region, located near the Swiss border south of Geneva.
  • D. Schorisse
    Schorisse is a village in East Flanders, Belgium, that now forms part of the municipality of Maarkedal.
  • E. Pont-en-Ogoz
    Pont-en-Ogoz is a Swiss municipality in the canton of Fribourg, known for its scenic setting on the shores of the Lake of Gruyère and its historic island with castle ruins and a church.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067995fc8190b048f15086bd42f0 completed April 15, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69fed32e425c819083f10f947c258a9b completed May 9, 2026, 6:24 a.m.
Created at: April 10, 2026, 3:09 a.m.