Triple
T35825388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dux Legnicensis |
E1035627
|
entity |
| Predicate | laterOverlordship |
P123303
|
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: [Dux Legnicensis, laterOverlordship, Kingdom of Bohemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterOverlordship Context triple: [Dux Legnicensis, laterOverlordship, Kingdom of Bohemia]
-
A.
overlordDuringReign
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
B.
laterUsurpedBy
chosen
Indicates that one entity, after some time has passed, is overthrown or replaced in power, position, or authority by another entity.
-
C.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
D.
laterHeir
Indicates that one entity becomes the heir of another at a later time, succeeding a prior heir or following a change in succession.
-
E.
overlordPower
Indicates that one entity holds dominant, controlling authority or power over another, often in a hierarchical or oppressive manner.
- 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_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:06 p.m.