Triple
T18287476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakşidil Sultan |
E438019
|
entity |
| Predicate | typeOfMonarchicRole |
P117093
|
FINISHED |
| Object | queen mother |
—
|
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: queen mother | Statement: [Nakşidil Sultan, typeOfMonarchicRole, queen mother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonarchicRole Context triple: [Nakşidil Sultan, typeOfMonarchicRole, queen mother]
-
A.
monarchicalRole
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
B.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
C.
typeOfMonarchyTitle
chosen
Indicates that a given title is a specific type or category of monarchy-related title (e.g., king, queen, emperor) within a monarchical system.
-
D.
symbolicRoleOfMonarch
Indicates that a monarch holds a primarily ceremonial or representational role rather than exercising substantive governing power.
-
E.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500faf62081908f16ebee0a195ba2 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.