Triple
T31259103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voivode (Poland) |
E797066
|
entity |
| Predicate | modernFormEstablished |
P8393
|
FINISHED |
| Object | after 1999 administrative reform of Poland |
—
|
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: after 1999 administrative reform of Poland | Statement: [Voivode (Poland), modernFormEstablished, after 1999 administrative reform of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernFormEstablished Context triple: [Voivode (Poland), modernFormEstablished, after 1999 administrative reform of Poland]
-
A.
modernFormSince
chosen
Indicates that an entity has existed in its current or modern form starting from a specified point in time.
-
B.
standardModernForm
Indicates that an entity is expressed or represented in the currently accepted standard modern form of a language, notation, or system.
-
C.
modernAccess
Indicates that an entity has contemporary, up-to-date means or methods of accessing or interacting with another entity or resource.
-
D.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
E.
modernNameForm
Indicates that one entity is the contemporary or currently used name form corresponding to another entity’s name.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 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: April 29, 2026, 9:12 p.m.