Triple
T7741257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljubljanica |
E175514
|
entity |
| Predicate | mouth |
P407
|
FINISHED |
| Object | Sava |
E75220
|
NE 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: Sava | Statement: [Ljubljanica, mouth, Sava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sava Context triple: [Ljubljanica, mouth, Sava]
-
A.
Sava
Sava is a European tire brand known for producing affordable, reliable tires, particularly popular in Central and Eastern Europe.
-
B.
Sava
Sava is a town and comune in the Province of Taranto in the Apulia region of southern Italy, known for its wine and olive oil production.
-
C.
Sava
chosen
Sava is a major river in Central and Southeastern Europe that flows through countries including Slovenia, Croatia, Bosnia and Herzegovina, and Serbia before joining the Danube.
-
D.
Sava
Sava is the monastic and religious name of Saint Sava, the medieval Serbian prince-turned-monk who became the first Archbishop of the autocephalous Serbian Orthodox Church and a key figure in Serbian religious and cultural history.
-
E.
Istra River
The Istra River is a waterway in the Moscow region of Russia that flows through the town of Istra before joining the Moskva River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6995f9c60819092e386192bd63c6f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7035df9348190ad3f3d845207bf4d |
completed | March 27, 2026, 10:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8f30c099081909aaeac321fbf0066 |
completed | March 29, 2026, 9:38 a.m. |
Created at: March 27, 2026, 4:07 p.m.