Triple
T26505566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sochi mountain cluster |
E669533
|
entity |
| Predicate | distanceFromSochiCoastalCluster |
P171403
|
FINISHED |
| Object | approximately 40 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 40 km | Statement: [Sochi mountain cluster, distanceFromSochiCoastalCluster, approximately 40 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSochiCoastalCluster Context triple: [Sochi mountain cluster, distanceFromSochiCoastalCluster, approximately 40 km]
-
A.
hasApproxDistanceFromSochiCenter
chosen
Indicates that one location is approximately a specified distance away from the center of Sochi.
-
B.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
C.
distanceToQatarCoast
Indicates the measured or calculated distance between a given location and the coastline of Qatar.
-
D.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
E.
distanceToRostovOnDon_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Rostov-on-Don.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 27, 2026, 1:16 a.m.