Triple
T37015618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strzyżów |
E916069
|
entity |
| Predicate | formerVoivodeship |
P112678
|
FINISHED |
| Object | Rzeszów Voivodeship |
—
|
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: Rzeszów Voivodeship | Statement: [Strzyżów, formerVoivodeship, Rzeszów Voivodeship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerVoivodeship Context triple: [Strzyżów, formerVoivodeship, Rzeszów Voivodeship]
-
A.
previousVoivodeship
Indicates that one voivodeship was the immediately preceding administrative region for another in a temporal or historical sequence.
-
B.
previousVoivodeshipCapital
Indicates that one entity served as the capital of a voivodeship before another capital or administrative change occurred.
-
C.
hasVoivode
Indicates that a region, territory, or administrative unit is governed or overseen by a specific voivode (provincial governor).
-
D.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
-
E.
hasVoivodeshipStatusInPast
chosen
Indicates that an entity previously held the status of a voivodeship (administrative region) but no longer does so.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00bc079314819096271bba60bee52d |
completed | May 10, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_6a00bba5bd408190ace5db0c4a90dc6f |
completed | May 10, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:14 p.m.