Triple
T17812494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzh River |
E444746
|
entity |
| Predicate | lengthInUkraine |
P129002
|
FINISHED |
| Object | 21.3 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: 21.3 km | Statement: [Uzh River, lengthInUkraine, 21.3 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthInUkraine Context triple: [Uzh River, lengthInUkraine, 21.3 km]
-
A.
lengthInPoland
Indicates that the specified length measurement is taken within the context or territory of Poland.
-
B.
distanceFromKyiv
Indicates the spatial distance between a given entity’s location and the city of Kyiv.
-
C.
lengthInCzechRepublic
Indicates the extent or measurement of something specifically within the geographic boundaries of the Czech Republic.
-
D.
lengthInHungary
Indicates that something has a specified length measured within the context or territory of Hungary.
-
E.
lengthInSlovakia
Indicates the extent or distance of something measured specifically within the territory of Slovakia.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887c63608190b29a407cabff0bc5 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.