Triple
T25647663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大日本帝国 |
E643007
|
entity |
| Predicate | 初代天皇 |
P155934
|
FINISHED |
| Object | 明治天皇 |
—
|
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: 明治天皇 | Statement: [大日本帝国, 初代天皇, 明治天皇]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 初代天皇 Context triple: [大日本帝国, 初代天皇, 明治天皇]
-
A.
traditionalFirstEmperor
chosen
Indicates that the subject is regarded, in traditional or legendary accounts, as the first emperor of the object polity or realm.
-
B.
traditionalFirstEmperorReignStart
Indicates the traditionally recognized starting date of the first emperor’s reign over a given polity or realm.
-
C.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
D.
hasNotableEmperor
Indicates that an entity is associated with at least one emperor who is historically recognized as particularly important or distinguished.
-
E.
就任時の天皇
Indicates the emperor who was reigning at the time someone assumed a position or office.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa6399c8190b24bba1b8ccc7bdc |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:57 p.m.