Triple
T20707407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flytoget airport express train |
E508940
|
entity |
| Predicate | travelTimeOsloSToAirport |
P39869
|
FINISHED |
| Object | about 19 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 19 minutes | Statement: [Flytoget airport express train, travelTimeOsloSToAirport, about 19 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelTimeOsloSToAirport Context triple: [Flytoget airport express train, travelTimeOsloSToAirport, about 19 minutes]
-
A.
approximateTravelTimeAirportToOsloS_minutes
Indicates the estimated duration, in minutes, required to travel from an airport to Oslo.
-
B.
distanceToOsloAirportGardermoen_km
Indicates the physical distance, measured in kilometers, between a given location and Oslo Airport Gardermoen.
-
C.
travelTimeToAirport
chosen
Indicates the amount of time required to travel from a given location to an airport.
-
D.
distanceFromOslo
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
E.
distanceToStockholmArlandaAirport
Indicates the measured distance between a given location or entity and Stockholm Arlanda Airport.
- F. None of above.
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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1917ce08190a54720d4d5b0a02c |
completed | April 21, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:14 p.m.