Triple
T224115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor’s Birthday |
E4277
|
entity |
| Predicate | hasDateUnderEmperor |
P9805
|
FINISHED |
| Object | February 23 (Emperor Naruhito) |
—
|
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: February 23 (Emperor Naruhito) | Statement: [Emperor’s Birthday, hasDateUnderEmperor, February 23 (Emperor Naruhito)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDateUnderEmperor Context triple: [Emperor’s Birthday, hasDateUnderEmperor, February 23 (Emperor Naruhito)]
-
A.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
B.
firstRecordedEmperorStatus
Indicates that the subject is recognized as the earliest historically recorded individual to hold the status or title of emperor.
-
C.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
-
D.
builtDuringReignOf
Indicates that something was constructed while a particular ruler or authority was in power.
-
E.
previousEmperorReignName
Indicates that the subject emperor’s reign name immediately precedes the object emperor’s reign name in historical 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dea93b48190863a3704b233aa03 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.