Triple
T21035273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Saxe-Hildburghausen |
E518172
|
entity |
| Predicate | titleHolderKnownAs |
P142563
|
FINISHED |
| Object | Therese of Bavaria |
—
|
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: Therese of Bavaria | Statement: [Duchess of Saxe-Hildburghausen, titleHolderKnownAs, Therese of Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderKnownAs Context triple: [Duchess of Saxe-Hildburghausen, titleHolderKnownAs, Therese of Bavaria]
-
A.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
titleHolderFullName
Indicates the full personal name of the entity that holds a particular title or position.
-
D.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
E.
titleHolderKnownFor
Indicates that the title holder is recognized or notable for a particular work, achievement, or characteristic.
- F. None of above. chosen
Provenance (4 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_69e0b503275c8190afd9a163f997c709 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc858d808190a8489aac801a4f51 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:02 p.m.