Triple
T4877550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soča River |
E109241
|
entity |
| Predicate | lengthInSlovenia |
P33049
|
FINISHED |
| Object | approximately 96 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 96 km | Statement: [Soča River, lengthInSlovenia, approximately 96 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthInSlovenia Context triple: [Soča River, lengthInSlovenia, approximately 96 km]
-
A.
localNameInSlovene
Indicates the name by which something is locally known or referred to in the Slovene language.
-
B.
distanceFromLjubljana
Indicates the spatial distance between an entity and the city of Ljubljana.
-
C.
lengthInKm
chosen
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
D.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
E.
distanceToŽilina_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Žilina.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.