Triple

T3661540
Position Surface form Disambiguated ID Type / Status
Subject Bodø E77659 entity
Predicate distanceToArcticCircleKmApprox P15650 FINISHED
Object 80 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: 80 | Statement: [Bodø, distanceToArcticCircleKmApprox, 80]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceToArcticCircleKmApprox
Context triple: [Bodø, distanceToArcticCircleKmApprox, 80]
  • A. distanceFromArcticCircle chosen
    Indicates the measured spatial separation between a given location and the Arctic Circle, typically expressed as a linear or angular distance.
  • B. distanceFromNorthPole
    Indicates the measured spatial distance between a given entity’s location and the geographic North Pole.
  • C. distanceFromEquator
    Indicates how far a location is from the Earth's equator, typically measured as a geographic or angular distance.
  • D. distanceFromSouthPole
    Indicates the measured distance of an entity from the geographic South Pole.
  • E. distanceToArkhangelskApproxKm
    Indicates the approximate distance, measured in kilometers, between a given entity’s location and Arkhangelsk.
  • 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_69ad85dfc4dc8190a441864202ab2a7a completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc3d826d88190b0b50e8592088a36 completed March 8, 2026, 6:45 p.m.
PD Predicate disambiguation batch_69adb847e9d881909dad2ffd0f3b6c15 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:25 p.m.