Triple
T14316362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | markrabě moravský |
E354965
|
entity |
| Predicate | historická role |
P29914
|
FINISHED |
| Object | zajištění královské moci na Moravě |
—
|
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: zajištění královské moci na Moravě | Statement: [markrabě moravský, historická role, zajištění královské moci na Moravě]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historická role Context triple: [markrabě moravský, historická role, zajištění královské moci na Moravě]
-
A.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
B.
hasHistoricalRoleAs
chosen
Indicates that an entity has served in a specific historical capacity, function, or position during a particular period or context.
-
C.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
D.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
E.
historicalFate
Indicates that two entities share a common or interconnected outcome, destiny, or consequence within a historical context.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.