Triple
T24610453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strzelce Opolskie |
E609097
|
entity |
| Predicate | hasSilesianName |
P156736
|
FINISHED |
| Object | Strzelce Uopolskie |
E609097
|
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: Strzelce Uopolskie | Statement: [Strzelce Opolskie, hasSilesianName, Strzelce Uopolskie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSilesianName Context triple: [Strzelce Opolskie, hasSilesianName, Strzelce Uopolskie]
-
A.
hasKashubianName
Indicates that an entity is associated with a specific name in the Kashubian language.
-
B.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
C.
hasSorbianName
Indicates that an entity has a name or designation expressed in the Sorbian language.
-
D.
hasNameInSlavonic
Indicates that an entity has a specific name or designation expressed in a Slavonic language.
-
E.
hasNameInLowerSorbian
Indicates that an entity has a specified name expressed in the Lower Sorbian language.
- F. None of above. chosen
Provenance (5 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0ff891a0e08190bf1feb5e18701543 |
completed | May 22, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.