Triple
T19725469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rygge municipality |
E473714
|
entity |
| Predicate | distanceToOsloApproxKm |
P15213
|
FINISHED |
| Object | about 60 |
—
|
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 60 | Statement: [Rygge municipality, distanceToOsloApproxKm, about 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToOsloApproxKm Context triple: [Rygge municipality, distanceToOsloApproxKm, about 60]
-
A.
distanceFromOslo
chosen
Indicates the spatial distance between a given entity’s location and the city of Oslo.
-
B.
distanceFromTrondheimApproximate
Indicates an approximate measure of how far something is from Trondheim, typically expressed as a rough or estimated distance rather than an exact value.
-
C.
distanceFromKristiansand
Indicates the spatial distance between a given location or object and the city of Kristiansand.
-
D.
distanceToOsloAirportGardermoen_km
Indicates the physical distance, measured in kilometers, between a given location and Oslo Airport Gardermoen.
-
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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649f7bedc81908f784832c0fc10a1 |
completed | April 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69e5304a7aac8190ac13f75f0c008e45 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:46 p.m.