Triple
T19281798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilibino Nuclear Power Plant |
E482205
|
entity |
| Predicate | distanceFromArcticCircle_km |
P15650
|
FINISHED |
| Object | approximately 100 |
—
|
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 100 | Statement: [Bilibino Nuclear Power Plant, distanceFromArcticCircle_km, approximately 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromArcticCircle_km Context triple: [Bilibino Nuclear Power Plant, distanceFromArcticCircle_km, approximately 100]
-
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.
distanceFromArcticOcean
Indicates the measured spatial distance between a given entity and the Arctic Ocean.
-
D.
distanceFromSouthPole
Indicates the measured distance of an entity from the geographic South Pole.
-
E.
distanceFromEquator
Indicates how far a location is from the Earth's equator, typically measured as a geographic or angular distance.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.