Triple
T13646921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Württemberg |
E326126
|
entity |
| Predicate | titleInMonarchyType |
P78578
|
FINISHED |
| Object | German monarchy |
—
|
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: German monarchy | Statement: [Duchess of Württemberg, titleInMonarchyType, German monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInMonarchyType Context triple: [Duchess of Württemberg, titleInMonarchyType, German monarchy]
-
A.
styleOfMonarchTitle
Indicates the specific formal style or wording used in the official title of a monarch.
-
B.
representativeOfMonarchTitle
Indicates that one entity serves as the official representative or holder of authority on behalf of a monarch’s title.
-
C.
royalTitularyFeature
chosen
Indicates that something is a characteristic or component element of a royal titulary (the formal set of titles held by a monarch).
-
D.
traditionalTitleOfKing
Indicates that the object is the customary or historically recognized royal title held by the king specified as the subject.
-
E.
kingConsortOfTitle
Indicates that a male monarch holds the position of king consort corresponding to a specific noble or royal title.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6073e888190965456a639839749 |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.