Triple
T16869179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Amsterdam high-speed corridor |
E410123
|
entity |
| Predicate | typicalTravelTimeParisAmsterdam |
P125297
|
FINISHED |
| Object | about 3 hours 20 minutes |
—
|
LITERAL 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: about 3 hours 20 minutes | Statement: [Paris–Amsterdam high-speed corridor, typicalTravelTimeParisAmsterdam, about 3 hours 20 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTravelTimeParisAmsterdam Context triple: [Paris–Amsterdam high-speed corridor, typicalTravelTimeParisAmsterdam, about 3 hours 20 minutes]
-
A.
distanceToAmsterdam
Indicates the spatial distance between a given location and the city of Amsterdam.
-
B.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
C.
travelTimeToParisByRER
Indicates the duration required to travel to Paris using the RER train network.
-
D.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
-
E.
directionFromAmsterdam
Indicates the cardinal or relative compass direction of an entity’s location as measured from Amsterdam.
- F. None of above. chosen
Provenance (4 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50a82348190b3e33fd558aa3c7f |
completed | April 18, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.