Triple
T16256185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyon–Rhône corridor |
E394633
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Lyon |
E15889
|
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: Lyon | Statement: [Lyon–Rhône corridor, terminus, Lyon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lyon Context triple: [Lyon–Rhône corridor, terminus, Lyon]
-
A.
Lyon
chosen
Lyon is a major city in east-central France known for its historical and architectural landmarks, gastronomy, and role as a key economic and cultural center.
-
B.
Lyon
Lyon is a historic Scottish noble family name most prominently associated with the Earls of Strathmore and Kinghorne.
-
C.
Lyons
Lyons is a small city in southeastern Georgia, United States, known as the administrative and commercial hub of Toombs County.
-
D.
Lyons
Lyons is a small town in northern Colorado known as a gateway to the Rocky Mountains and for its vibrant music and arts scene.
-
E.
Lyons
Lyons is a sports team or athletic program associated with Wheaton College, commonly referred to by this shortened name.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2459a48f081909c76b38741b8f04e |
completed | April 17, 2026, 2:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007d9a8d7481908c7bc4711ddacc13 |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 5:04 a.m.