Triple
T8098736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgian railway line 161 |
E189051
|
entity |
| Predicate | serves |
P98
|
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: [Belgian railway line 161, serves, Arlon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arlon Context triple: [Belgian railway line 161, serves, 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.
Murten
Murten is a historic bilingual town in the canton of Fribourg, Switzerland, known for its well-preserved medieval old town and lakeside setting on Lake Murten.
-
E.
Rixensart
Rixensart is a municipality in Walloon Brabant, Belgium, known for its residential character and proximity to Brussels.
- 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_69ca82b886d88190a9cba0d5a4a27521 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42961ad4819085d023427fc5ac5f |
completed | March 31, 2026, 3:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd677b00548190929a2a38b4d1476f |
completed | April 1, 2026, 6:44 p.m. |
Created at: March 30, 2026, 5:30 p.m.