Triple
T9724447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soła River |
E235567
|
entity |
| Predicate | hasPolishName |
P15778
|
FINISHED |
| Object | Soła |
E607778
|
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: Soła | Statement: [Soła River, hasPolishName, Soła]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soła Context triple: [Soła River, hasPolishName, Soła]
-
A.
Soła
chosen
Soła is a river in southern Poland that flows through the Silesian region before joining the Vistula.
-
B.
Soła Oświęcim
Soła Oświęcim is a Polish sports club based in the town of Oświęcim, best known for its football team competing in the lower national leagues.
-
C.
Łeba
Łeba is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Sopot
Sopot is a suburban municipality of Belgrade, Serbia, known for its rural character and proximity to the Avala and Kosmaj mountains.
-
E.
Sopot
Sopot is a Polish Baltic Sea resort city famous for its sandy beaches, long wooden pier, and vibrant spa and nightlife culture.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e77096481908ffd315fecb1d5ec |
completed | April 1, 2026, 10:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19faa064081909c1d23044984a17c |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:21 p.m.