Triple
T22140039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Podolínec |
E547132
|
entity |
| Predicate | formerPrivilege |
P147133
|
FINISHED |
| Object | royal privileges |
—
|
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: royal privileges | Statement: [Podolínec, formerPrivilege, royal privileges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerPrivilege Context triple: [Podolínec, formerPrivilege, royal privileges]
-
A.
formerAccess
Indicates that an entity previously had access to another entity or resource but no longer does.
-
B.
holderPrivileges
Indicates that one entity possesses specific rights, permissions, or advantages granted to the holder of another entity.
-
C.
formerConcessionOf
Indicates that one entity was previously a concession (a leased or granted area or operation) controlled by another entity, but no longer holds that status.
-
D.
formerDesignation
Indicates that an entity previously held a particular title, role, or designation that it no longer holds.
-
E.
lostPrivilegesDuring
Indicates that an entity had certain privileges revoked or suspended for the duration of a specified time period or event.
- F. None of above. chosen
Provenance (4 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bda1208190b851ae5c68b760e9 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.