Triple
T27476797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三木武夫 |
E693484
|
entity |
| Predicate | 天皇 |
P67018
|
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.
就任時の天皇
chosen
Indicates the emperor who was reigning at the time someone assumed a position or office.
-
B.
退任時の天皇
Indicates the relationship in which a person holds the status of emperor at the time of their abdication or retirement from the throne.
-
C.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
-
D.
hasNotableEmperor
Indicates that an entity is associated with at least one emperor who is historically recognized as particularly important or distinguished.
-
E.
successorInJapan
Indicates that one entity directly follows or replaces another in a role, position, or sequence within the context of Japan.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e451dd08190b9cbe3a9a2a4ffa6 |
completed | May 2, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:57 p.m.