Triple
T32908487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rovno |
E841806
|
entity |
| Predicate | standardizedNameInPolish |
P16476
|
FINISHED |
| Object | Równe |
—
|
NE NERFINISHED |
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: Równe | Statement: [Rovno, standardizedNameInPolish, Równe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizedNameInPolish Context triple: [Rovno, standardizedNameInPolish, Równe]
-
A.
hasNameInPolish
Indicates that an entity is associated with a specific name or label expressed in the Polish language.
-
B.
officialNamePolish
chosen
Indicates the official or legally recognized name of an entity as expressed in the Polish language.
-
C.
isEquivalentSurnameInPolish
Indicates that two surnames are equivalent to each other when translated, adapted, or used in the Polish language.
-
D.
hasSilesianName
Indicates that an entity is associated with a name expressed in the Silesian language.
-
E.
isPolish
Indicates that an entity has the property of being Polish, typically in terms of nationality, origin, or cultural affiliation.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:19 a.m.