Triple
T4638655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Majesty The Empress |
E101595
|
entity |
| Predicate | formalTitleFor |
P30521
|
FINISHED |
| Object | Empress consort of Japan |
—
|
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: Empress consort of Japan | Statement: [Her Majesty The Empress, formalTitleFor, Empress consort of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalTitleFor Context triple: [Her Majesty The Empress, formalTitleFor, Empress consort of Japan]
-
A.
usedInFormalTitleOf
chosen
Indicates that something is employed as part of the official or formal title of an entity.
-
B.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
C.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
-
D.
formalTitleInLuxembourgish
Indicates that an entity holds a specific formal or official title expressed in the Luxembourgish language.
-
E.
namedForTitle
Indicates that one entity is named after or in honor of the title (such as a rank, honorific, or formal designation) associated with 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.