Triple
T1047209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslo Airport, Gardermoen |
E22608
|
entity |
| Predicate | distanceToOsloByRoad_km |
P15213
|
FINISHED |
| Object | about 47 |
—
|
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 47 | Statement: [Oslo Airport, Gardermoen, distanceToOsloByRoad_km, about 47]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOsloByRoad_km Context triple: [Oslo Airport, Gardermoen, distanceToOsloByRoad_km, about 47]
-
A.
distanceFromOslo
chosen
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
B.
distanceToHelsinki_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Helsinki.
-
C.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
D.
distanceFromStockholmCityCentre
Indicates the measured distance between a given location and the center of Stockholm city.
-
E.
approximateDistanceKm
Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.