Triple
T25484903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Værnes Station |
E638676
|
entity |
| Predicate | distanceFromTrondheim |
P65887
|
FINISHED |
| Object | approximately 32 km |
—
|
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: approximately 32 km | Statement: [Værnes Station, distanceFromTrondheim, approximately 32 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTrondheim Context triple: [Værnes Station, distanceFromTrondheim, approximately 32 km]
-
A.
distanceFromTrondheimApproximate
chosen
Indicates an approximate measure of how far something is from Trondheim, typically expressed as a rough or estimated distance rather than an exact value.
-
B.
distanceFromOslo
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
C.
distanceFromKristiansand
Indicates the spatial distance between a given location or object and the city of Kristiansand.
-
D.
distanceFromStavanger
Indicates the spatial distance between a given entity or location and the city of Stavanger.
-
E.
distanceToTromsø_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the location of Tromsø.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 21, 2026, 2:32 p.m.