Triple
T16950101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lazeshchyna |
E411158
|
entity |
| Predicate | distanceToHoverla |
P125353
|
FINISHED |
| Object | approximately 15–20 kilometres by hiking routes |
—
|
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 kilometres by hiking routes | Statement: [Lazeshchyna, distanceToHoverla, approximately 15–20 kilometres by hiking routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHoverla Context triple: [Lazeshchyna, distanceToHoverla, approximately 15–20 kilometres by hiking routes]
-
A.
distanceToPahiatua
Indicates the measured spatial distance between a given location and the place referred to as Pahiatua.
-
B.
landingDistance
Indicates the required or actual distance needed for an aircraft or object to complete a landing from approach to full stop.
-
C.
distanceFromHadibu
Indicates the spatial distance between a given entity and the location of Hadibu.
-
D.
distanceToPula
Indicates the measured or calculated spatial distance between a given entity and the location Pula.
-
E.
distanceToHampi
Indicates the measured or specified distance between a given entity or location and Hampi.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfb570b08190ae3385b0cad32668 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.