Triple
T27349167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiev Voivodeship |
E684308
|
entity |
| Predicate | hadNumberOfDeputiesToSejm |
P80248
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Kiev Voivodeship, hadNumberOfDeputiesToSejm, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNumberOfDeputiesToSejm Context triple: [Kiev Voivodeship, hadNumberOfDeputiesToSejm, 2]
-
A.
hasNumberOfDeputies
chosen
Indicates the specific count of deputies associated with or assigned to an entity.
-
B.
hasVoivodeshipSejmik
Indicates that an entity is associated with, or falls under the jurisdiction of, a specific voivodeship sejmik (regional legislative assembly).
-
C.
servedAsMarshalOfTheSejmStart
Indicates the time when a person began serving in the role of Marshal (presiding officer) of the Sejm.
-
D.
hasVoivode
Indicates that a region, territory, or administrative unit is governed or overseen by a specific voivode (provincial governor).
-
E.
servedAsMarshalOfTheSejmEnd
Indicates that a person’s tenure in the role of Marshal (speaker/presiding officer) of the Sejm has ended at a specified time or event.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba5a110819092fe773ade8fec2e |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:47 a.m.