Triple
T18115921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Bohemia |
E433603
|
entity |
| Predicate | legalStatusWithinEmpire |
P40055
|
FINISHED |
| Object | imperial fief |
—
|
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: imperial fief | Statement: [Duchy of Bohemia, legalStatusWithinEmpire, imperial fief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusWithinEmpire Context triple: [Duchy of Bohemia, legalStatusWithinEmpire, imperial fief]
-
A.
legalStatusInEmpire
chosen
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
B.
legalStatusOfTerritoryAdministered
Indicates the legal status or standing of a territory that is under a particular administration or governing authority.
-
C.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
D.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
E.
sovereigntyRegime
Indicates the type or structure of political authority and control exercised over a territory or population.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd58ea8819081e2bec5e591e093 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.