Triple
T18713651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miramas |
E457579
|
entity |
| Predicate | servedByRailLines |
P782
|
FINISHED |
| Object | Marseille–Arles–Avignon axis |
—
|
NE NERFINISHED |
How this triple was built (3 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: Marseille–Arles–Avignon axis | Statement: [Miramas, servedByRailLines, Marseille–Arles–Avignon axis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marseille–Arles–Avignon axis Context triple: [Miramas, servedByRailLines, Marseille–Arles–Avignon axis]
-
A.
Lyon–Marseille axis
The Lyon–Marseille axis is a major French railway corridor linking the cities of Lyon and Marseille and serving as a key north–south route in southeastern France.
-
B.
Lyon–Grenoble axis
The Lyon–Grenoble axis is a major urban and economic corridor in southeastern France linking the metropolitan areas of Lyon and Grenoble through a chain of intermediate towns and infrastructure.
-
C.
Lyon–Rhône corridor
The Lyon–Rhône corridor is a major inland waterway route in France that links the city of Lyon to the Rhône River, facilitating north–south freight and passenger transport between central Europe and the Mediterranean.
-
D.
Bordeaux–Toulouse–Marseille
Bordeaux–Toulouse–Marseille is a major French intercity rail corridor linking the Atlantic city of Bordeaux with Toulouse and the Mediterranean port of Marseille.
-
E.
Cannes–Grasse–Antibes conurbation
The Cannes–Grasse–Antibes conurbation is a densely populated urban area on the French Riviera that links the coastal cities of Cannes and Antibes with the inland town of Grasse into a continuous metropolitan zone.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Marseille–Arles–Avignon axis Target entity description: The Marseille–Arles–Avignon axis is a major railway corridor in southern France linking the coastal city of Marseille with the inland cities of Arles and Avignon.
-
A.
Lyon–Marseille axis
The Lyon–Marseille axis is a major French railway corridor linking the cities of Lyon and Marseille and serving as a key north–south route in southeastern France.
-
B.
Lyon–Grenoble axis
The Lyon–Grenoble axis is a major urban and economic corridor in southeastern France linking the metropolitan areas of Lyon and Grenoble through a chain of intermediate towns and infrastructure.
-
C.
Lyon–Rhône corridor
The Lyon–Rhône corridor is a major inland waterway route in France that links the city of Lyon to the Rhône River, facilitating north–south freight and passenger transport between central Europe and the Mediterranean.
-
D.
Bordeaux–Toulouse–Marseille
Bordeaux–Toulouse–Marseille is a major French intercity rail corridor linking the Atlantic city of Bordeaux with Toulouse and the Mediterranean port of Marseille.
-
E.
Cannes–Grasse–Antibes conurbation
The Cannes–Grasse–Antibes conurbation is a densely populated urban area on the French Riviera that links the coastal cities of Cannes and Antibes with the inland town of Grasse into a continuous metropolitan zone.
- F. None of above. chosen
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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab352b481909b444e7c476898f4 |
completed | April 19, 2026, 11:52 p.m. |
Created at: April 10, 2026, 11:50 a.m.