Triple
T29019220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganina Yama |
E737404
|
entity |
| Predicate | distanceFromYekaterinburg |
P196537
|
FINISHED |
| Object | approximately 15–20 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 15–20 km | Statement: [Ganina Yama, distanceFromYekaterinburg, approximately 15–20 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromYekaterinburg Context triple: [Ganina Yama, distanceFromYekaterinburg, approximately 15–20 km]
-
A.
distanceToYekaterinburg_km
chosen
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Yekaterinburg.
-
B.
distanceToIrkutsk_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Irkutsk.
-
C.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
D.
distanceToYakutsk
Indicates the spatial distance between a given entity and the location of Yakutsk.
-
E.
distanceToYoshkarOla_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Yoshkar-Ola.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: April 28, 2026, 9:48 a.m.