Triple
T35643208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchy of Legnica |
E1029929
|
entity |
| Predicate | wasVassalStateOf |
P47437
|
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: [Duchy of Legnica, wasVassalStateOf, Kingdom of Bohemia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasVassalStateOf Context triple: [Duchy of Legnica, wasVassalStateOf, Kingdom of Bohemia]
-
A.
vassalState
chosen
Indicates a relationship where one political entity is subordinate to and under the authority or control of another, typically more powerful, state.
-
B.
isColonialFoundationOf
Indicates that one entity was established as a colony that later developed into or served as the origin of the other entity.
-
C.
wasCoreTerritoryOf
Indicates that a region historically formed the central or most important territorial area belonging to a particular political or cultural entity.
-
D.
formerColonialStatus
Indicates that one entity previously held colonial authority or control over another entity, but that colonial relationship has since ended.
-
E.
wasColonialPower
Indicates that one entity historically exercised colonial control or dominance over another entity.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f4d48548190a2b332aefc390b01 |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.