Triple
T4447120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Union |
E96315
|
entity |
| Predicate | operatedRoute |
P18593
|
FINISHED |
| Object | Paris–Lille |
E87143
|
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: Paris–Lille | Statement: [Air Union, operatedRoute, Paris–Lille]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paris–Lille Context triple: [Air Union, operatedRoute, Paris–Lille]
-
A.
Paris–Lille
chosen
Paris–Lille is a major high-speed rail corridor in northern France connecting the capital Paris with the city of Lille.
-
B.
Paris–Strasbourg
Paris–Strasbourg is a major high-speed rail corridor in France linking the capital with the Alsatian city near the German border.
-
C.
Paris–Toulouse
Paris–Toulouse is a major intercity rail corridor in France linking the capital Paris with the southwestern city of Toulouse.
-
D.
Paris–Bordeaux
Paris–Bordeaux is a major high-speed rail corridor in France connecting the capital with the southwest, known for its fast TGV services.
-
E.
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.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d31e10819086590b9f828d50b0 |
completed | March 13, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b62818295481909c0ffa377570effc |
completed | March 15, 2026, 3:31 a.m. |
Created at: March 12, 2026, 11:32 p.m.