Triple
T12021886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharabali |
E286171
|
entity |
| Predicate | distanceToAstrakhan |
P102826
|
FINISHED |
| Object | approximately 140 km northwest of Astrakhan |
—
|
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 140 km northwest of Astrakhan | Statement: [Kharabali, distanceToAstrakhan, approximately 140 km northwest of Astrakhan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAstrakhan Context triple: [Kharabali, distanceToAstrakhan, approximately 140 km northwest of Astrakhan]
-
A.
distanceToRostovOnDon_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Rostov-on-Don.
-
B.
distanceToGrozny_km
Indicates the physical distance, measured in kilometers, between a given location and the city of Grozny.
-
C.
distanceToKhiva
Indicates the spatial distance between a given location or object and the city of Khiva.
-
D.
distanceFromMoscow_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Moscow.
-
E.
distanceToKostroma
Indicates the spatial distance between a given entity and the location of Kostroma.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.