Triple
T25059276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess Palatine of the Rhine |
E627610
|
entity |
| Predicate | titleUsedByDynasty |
P126784
|
FINISHED |
| Object | House of Wittelsbach |
—
|
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: House of Wittelsbach | Statement: [Countess Palatine of the Rhine, titleUsedByDynasty, House of Wittelsbach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleUsedByDynasty Context triple: [Countess Palatine of the Rhine, titleUsedByDynasty, House of Wittelsbach]
-
A.
usedDuringDynasty
Indicates that something (such as an object, practice, or concept) was in use during the time period of a specific dynasty.
-
B.
dynasticUse
chosen
Indicates the use of something (such as a name, title, symbol, or resource) in a way that is tied to or characteristic of a particular dynasty or ruling family.
-
C.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
D.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
E.
existedUnderDynasty
Indicates that an entity existed or was in effect during the period of a specified dynasty’s 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 6:09 a.m.