Triple
T14951710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austevoll archipelago |
E372808
|
entity |
| Predicate | distanceToBergen |
P116810
|
FINISHED |
| Object | approximately 30–40 km southwest |
—
|
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 30–40 km southwest | Statement: [Austevoll archipelago, distanceToBergen, approximately 30–40 km southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBergen Context triple: [Austevoll archipelago, distanceToBergen, approximately 30–40 km southwest]
-
A.
distanceFromOslo
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.
distanceToDrammen
Indicates the measured distance between a given entity and the location Drammen.
-
D.
distanceFromKristiansand
Indicates the spatial distance between a given location or object and the city of Kristiansand.
-
E.
distanceFromBodø
Indicates the spatial distance between a given entity and the location of Bodø.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded690f2e08190ad9dad6dc05a164a |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:39 a.m.