Triple
T682336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Estates |
E13208
|
entity |
| Predicate | wereSubjectTo |
P1313
|
FINISHED |
| Object | authority of the Holy Roman Emperor |
—
|
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: authority of the Holy Roman Emperor | Statement: [Imperial Estates, wereSubjectTo, authority of the Holy Roman Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereSubjectTo Context triple: [Imperial Estates, wereSubjectTo, authority of the Holy Roman Emperor]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
decisionsSubjectTo
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
C.
underwent
Indicates that an entity experienced or was subjected to a process, event, or change, typically as the patient of an action.
-
D.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
E.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06f9ee88190a2d757aacd8e3f5b |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.