Triple
T14316349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | markrabě moravský |
E354965
|
entity |
| Predicate | kompetence |
P18508
|
FINISHED |
| Object | správa země Moravy |
—
|
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: správa země Moravy | Statement: [markrabě moravský, kompetence, správa země Moravy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kompetence Context triple: [markrabě moravský, kompetence, správa země Moravy]
-
A.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
B.
competenceArea
chosen
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
C.
definesCompetenceOf
Indicates that one entity specifies, determines, or establishes the scope, level, or nature of another entity’s competence or capability.
-
D.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
E.
sharesCompetencesWith
Indicates that two entities possess and can apply the same or overlapping set of skills, abilities, or areas of expertise.
- 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.