Triple
T31259101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voivode (Poland) |
E797066
|
entity |
| Predicate | existsInNumberOfUnits |
P19248
|
FINISHED |
| Object | 16 voivodeships |
—
|
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: 16 voivodeships | Statement: [Voivode (Poland), existsInNumberOfUnits, 16 voivodeships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existsInNumberOfUnits Context triple: [Voivode (Poland), existsInNumberOfUnits, 16 voivodeships]
-
A.
hasQuantityInStandardSet
Indicates that an entity possesses a specified amount or count expressed according to a defined standard set or unit system.
-
B.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
C.
numberOfUnits
chosen
Indicates the quantity or count of discrete units associated with an entity or relationship.
-
D.
inventoryNumberAt
Indicates that a specific inventory number is assigned to an entity at a particular location or point in time.
-
E.
isPerceivedQuantity
Indicates that a quantity is understood, interpreted, or experienced by an observer rather than being an objective or directly measured amount.
- 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_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.