Triple
T27399960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Schleswig-Holstein-Sonderburg-Augustenburg |
E691804
|
entity |
| Predicate | titleHolderEmpressFrom |
P37710
|
FINISHED |
| Object | 1888 |
—
|
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: 1888 | Statement: [Princess of Schleswig-Holstein-Sonderburg-Augustenburg, titleHolderEmpressFrom, 1888]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderEmpressFrom Context triple: [Princess of Schleswig-Holstein-Sonderburg-Augustenburg, titleHolderEmpressFrom, 1888]
-
A.
associatedEmpress
Indicates a relationship where an empress is linked or connected to another entity, such as a person, place, event, or object, in a relevant or context-specific way.
-
B.
eraAsEmpress
chosen
Indicates the time period during which a person held the role or status of empress.
-
C.
realmAsEmpress
Indicates that an entity holds the position or role of empress over a specified realm or domain.
-
D.
reignAsEmpress
Indicates that a person holds and exercises the supreme imperial authority in the role of empress over a realm or empire.
-
E.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: April 27, 2026, 12:29 p.m.