Triple
T33941225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Takakura |
E870169
|
entity |
| Predicate | ordinalInMonarchy |
P97834
|
FINISHED |
| Object | 80th Emperor 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: 80th Emperor of Japan | Statement: [Emperor Takakura, ordinalInMonarchy, 80th Emperor of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalInMonarchy Context triple: [Emperor Takakura, ordinalInMonarchy, 80th Emperor of Japan]
-
A.
monarchicRank
chosen
Indicates the hierarchical level or status an individual holds within a monarchical system of rule.
-
B.
rankInPrincelyOrder
Indicates the position or level an entity holds within a specified princely order or hierarchy.
-
C.
positionInLineOfSuccessionToThrone
Indicates the ordinal place an individual holds in the ordered sequence of heirs eligible to inherit a throne.
-
D.
epithetOfMonarchNumber
Indicates that a particular epithet (descriptive title or nickname) is associated with a specific numbered monarch in a royal succession.
-
E.
dynasticOrder
Indicates the hierarchical sequence of rulers or family lines within a dynasty, specifying who precedes or follows whom in dynastic succession.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.