Triple
T17768065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blériot-SPAD S.46 |
E443561
|
entity |
| Predicate | usedOnRoute |
P21808
|
FINISHED |
| Object | Paris–Amsterdam |
—
|
NE NERFINISHED |
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–Amsterdam | Statement: [Blériot-SPAD S.46, usedOnRoute, Paris–Amsterdam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paris–Amsterdam Context triple: [Blériot-SPAD S.46, usedOnRoute, Paris–Amsterdam]
-
A.
Paris–Amsterdam
chosen
Paris–Amsterdam is a major international high-speed rail route linking the capitals of France and the Netherlands.
-
B.
Paris–Brussels
Paris–Brussels is a major international high-speed rail corridor linking the capitals of France and Belgium.
-
C.
London–Amsterdam
London–Amsterdam is a major international rail route connecting the capital cities of the United Kingdom and the Netherlands.
-
D.
Vienna–Amsterdam
Vienna–Amsterdam is an international overnight train route connecting Austria’s capital with the Netherlands’ largest city.
-
E.
Cologne–Paris
Cologne–Paris is a former low-cost international air route connecting the German city of Cologne with the French capital, Paris.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fd8aa081909c8ee9264af15c69 |
completed | April 19, 2026, 7:36 a.m. |
Created at: April 10, 2026, 10:11 a.m.