Triple
T31259093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voivode (Poland) |
E797066
|
entity |
| Predicate | mayDelegatePowersTo |
P3670
|
FINISHED |
| Object | vice-voivode |
—
|
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: vice-voivode | Statement: [Voivode (Poland), mayDelegatePowersTo, vice-voivode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayDelegatePowersTo Context triple: [Voivode (Poland), mayDelegatePowersTo, vice-voivode]
-
A.
mayDelegateTo
Indicates that one entity is permitted to transfer or assign its authority, responsibility, or rights to another entity.
-
B.
canDelegateTo
chosen
Indicates that one entity has the authority or ability to transfer or assign its responsibilities, tasks, or decision-making power to another entity.
-
C.
maySendDelegationsTo
Indicates that one entity is permitted or authorized to dispatch an official group or representative delegation to another entity.
-
D.
mayBeDelegatedTo
Indicates that a responsibility, task, or authority can be transferred from one entity to another to act on its behalf.
-
E.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
- 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.