Triple
T27722228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landgrave of Thuringia |
E698987
|
entity |
| Predicate | heldRankInImperialDiet |
P44656
|
FINISHED |
| Object | princely seat |
—
|
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: princely seat | Statement: [Landgrave of Thuringia, heldRankInImperialDiet, princely seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldRankInImperialDiet Context triple: [Landgrave of Thuringia, heldRankInImperialDiet, princely seat]
-
A.
hasPositionInImperialDiet
chosen
Indicates that an entity holds or held a formal seat or role within the Imperial Diet.
-
B.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
C.
hadMemberInImperialFamily
Indicates that an entity had at least one member belonging to an imperial family.
-
D.
rankInPrincelyOrder
Indicates the position or level an entity holds within a specified princely order or hierarchy.
-
E.
monarchicRank
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363d2d608190a1128b7326403028 |
completed | May 2, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:07 p.m.