Triple
T7503080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biała River |
E177313
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Biała |
E609845
|
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: Biała | Statement: [Biała River, hasNameInLanguage, Biała]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biała Context triple: [Biała River, hasNameInLanguage, Biała]
-
A.
Biała
Biała is a former town in southern Poland that historically developed as a separate urban center before being merged with Bielsko to form the modern city of Bielsko-Biała.
-
B.
Biała Piska
Biała Piska is a small town in northeastern Poland known for its location amid the lakes and forests of the Warmian-Masurian region.
-
C.
Słupia
Słupia is a river in northern Poland that flows through the Pomeranian region to the Baltic Sea.
-
D.
Biała Lądecka
chosen
Biała Lądecka is a river in southwestern Poland that flows through the Kłodzko region before joining the Nysa Kłodzka.
-
E.
Mława
Mława is a town in north-central Poland known for its historical significance, including a major World War II battle, and its regional cultural and economic role.
- 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_69c69f2696688190915a8458f2398211 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5b32c708190bb3a92d0d949304a |
completed | March 27, 2026, 9:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c83c9953e88190a1e0e899f2ddf822 |
completed | March 28, 2026, 8:39 p.m. |
Created at: March 27, 2026, 3:44 p.m.