Triple
T17074311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bukowno |
E414308
|
entity |
| Predicate | hasNameInLanguage |
P15
|
FINISHED |
| Object | Bukowno@pl |
E414308
|
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: Bukowno@pl | Statement: [Bukowno, hasNameInLanguage, Bukowno@pl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bukowno@pl Context triple: [Bukowno, hasNameInLanguage, Bukowno@pl]
-
A.
Bukowno
chosen
Bukowno is a town in southern Poland known for its industrial character and location within the Lesser Poland Voivodeship.
-
B.
Polish Wikibooks
Polish Wikibooks is the Polish-language edition of the Wikibooks project, offering a collection of free, collaboratively written open-content textbooks and manuals.
-
C.
Łabuńka
Łabuńka is a river in southeastern Poland that flows through the Lublin Voivodeship, including the area around the city of Zamość.
-
D.
Sokołówka
Sokołówka is a small river in Poland known for flowing through the city of Łódź and its surrounding areas.
-
E.
Gmina Bukowno
Gmina Bukowno is an urban-rural administrative district in southern Poland, located within the Lesser Poland Voivodeship.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc3b69c819093b32da3998eed46 |
completed | April 18, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ede108881909ddd0455be53ffac |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:34 a.m.