Triple
T855614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Taishō |
E18484
|
entity |
| Predicate | eraCharacterMeaning |
P11402
|
FINISHED |
| Object | great righteousness |
—
|
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: great righteousness | Statement: [Emperor Taishō, eraCharacterMeaning, great righteousness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraCharacterMeaning Context triple: [Emperor Taishō, eraCharacterMeaning, great righteousness]
-
A.
inscriptionMeaning
chosen
Indicates that an inscription conveys a particular meaning, message, or content.
-
B.
equivalentInRomanMythology
Indicates that one entity corresponds to or is identified as the Roman-mythology counterpart of another entity from a different mythological tradition.
-
C.
reasonForEpithet
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
D.
characterIn
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
E.
callSignMeaning
Indicates that an entity’s call sign conveys or is associated with a particular meaning or interpretation.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac3c172481908ed164ee1579ec28 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.