Triple
T9304596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Worms |
E223849
|
entity |
| Predicate | wasImperialImmediate |
P45698
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prince-Bishopric of Worms, wasImperialImmediate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasImperialImmediate Context triple: [Prince-Bishopric of Worms, wasImperialImmediate, true]
-
A.
heldImperialImmediacy
chosen
Indicates that an entity possessed imperial immediacy, meaning it was directly subject to the authority of the emperor rather than to any intermediate feudal lord.
-
B.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
C.
fatherWasEmperorOf
Indicates that the person referred to as the father held the position or title of emperor of the specified entity (such as a state, empire, or territory).
-
D.
wasHegemonOf
Indicates that one entity held dominant political, military, or economic leadership over another entity or group.
-
E.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1da623ac81908bab6dfb1bbce25d |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.