Triple
T541670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Masako |
E12642
|
entity |
| Predicate | becameCrownPrincessOn |
P15467
|
FINISHED |
| Object | 1993-06-09 |
—
|
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: 1993-06-09 | Statement: [Empress Masako, becameCrownPrincessOn, 1993-06-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameCrownPrincessOn Context triple: [Empress Masako, becameCrownPrincessOn, 1993-06-09]
-
A.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
B.
successorAsQueenConsort
Indicates that one individual became the next queen consort following another in a royal succession.
-
C.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
D.
heirPresumptiveBeforeAccession
Indicates that one entity was the designated heir presumptive to another entity before that other entity formally acceded to a position, title, or office.
-
E.
predecessorAsQueenConsort
Indicates that one queen consort held the position immediately before another queen consort in a royal succession.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49861195081909540eaf402a5401a |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.