Triple
T25647653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 大日本帝国 |
E643007
|
entity |
| Predicate | 君主制の形態 |
P21959
|
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.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
-
B.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
C.
constitutionalMonarchyFeature
Indicates that the subject possesses a characteristic or institutional element typical of a constitutional monarchy system of government.
-
D.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
E.
constitutionalMonarchyEstablished
Indicates that a constitutional monarchy as a system of government has been formally created or brought into existence.
- 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.