Triple
T34950621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobrowniki–Berestovitsa |
E1007980
|
entity |
| Predicate | hasLanguageOnPolishSide |
P103974
|
FINISHED |
| Object | Polish |
—
|
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: Polish | Statement: [Bobrowniki–Berestovitsa, hasLanguageOnPolishSide, Polish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOnPolishSide Context triple: [Bobrowniki–Berestovitsa, hasLanguageOnPolishSide, Polish]
-
A.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
-
B.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
C.
hasLanguageOfSide
chosen
Indicates that an entity uses or is associated with a particular language on a specific side or aspect (e.g., one side of a bilingual object or interface).
-
D.
hasSilesianName
Indicates that an entity is associated with a name expressed in the Silesian language.
-
E.
hasKashubianName
Indicates that an entity is associated with a specific name in the Kashubian language.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 4 p.m.