Triple
T25503836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolyma Hydroelectric Station |
E639192
|
entity |
| Predicate | distanceToMagadan |
P181628
|
FINISHED |
| Object | approximately 1800 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 1800 km | Statement: [Kolyma Hydroelectric Station, distanceToMagadan, approximately 1800 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMagadan Context triple: [Kolyma Hydroelectric Station, distanceToMagadan, approximately 1800 km]
-
A.
distanceToPetropavlovskKamchatsky
Indicates the spatial distance between an entity and the location of Petropavlovsk-Kamchatsky.
-
B.
distanceFromMurmansk
Indicates the spatial distance between a given location and the city of Murmansk.
-
C.
distanceToVladivostok_km
Indicates the physical distance, measured in kilometers, between a given location and Vladivostok.
-
D.
distanceToSakhalinApprox
Indicates an approximate measured or estimated distance between an entity and Sakhalin.
-
E.
distanceToYamalPeninsula
Indicates the measured or calculated distance between a given entity’s location and the Yamal Peninsula.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 21, 2026, 2:46 p.m.