Triple
T34952055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Lucemburský |
E1008025
|
entity |
| Predicate | vládlV |
P60298
|
FINISHED |
| Object | Království české |
—
|
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: Království české | Statement: [Jan Lucemburský, vládlV, Království české]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vládlV Context triple: [Jan Lucemburský, vládlV, Království české]
-
A.
vakul
Indicates a relationship or action between entities, but the specific meaning of the predicate "vakul" is unclear without additional context or definition.
-
B.
rulerOf
chosen
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
vadi
Indicates that one entity is speaking, arguing, or verbally expressing something to another entity.
-
D.
victor
Indicates that one entity is the winner or has prevailed over another in a contest, conflict, or competition.
-
E.
vise
Indicates that one entity firmly grips, clamps, or holds another in place, typically restricting its movement or separating it from other objects.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782cea4c881908ada116c80eafa15 |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.