Triple
T35595172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Głogów |
E1028609
|
entity |
| Predicate | becameFiefOf |
P87619
|
FINISHED |
| Object | Kingdom of Bohemia |
—
|
NE NERFINISHED |
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: Kingdom of Bohemia | Statement: [Duchy of Głogów, becameFiefOf, Kingdom of Bohemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameFiefOf Context triple: [Duchy of Głogów, becameFiefOf, Kingdom of Bohemia]
-
A.
formerFiefOf
chosen
Indicates that a territory or domain was previously under the control or jurisdiction of a specified lord, ruler, or political entity as a fief.
-
B.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
C.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
D.
vassalsOf
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
E.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.