Triple
T105651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Japan |
E2130
|
entity |
| Predicate | postWorldWarIIRole |
P4701
|
FINISHED |
| Object | constitutional monarch |
—
|
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: constitutional monarch | Statement: [Emperor of Japan, postWorldWarIIRole, constitutional monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWorldWarIIRole Context triple: [Emperor of Japan, postWorldWarIIRole, constitutional monarch]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
legalStatusAfterWar
chosen
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
C.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
D.
statusDuringColdWar
Indicates the political or diplomatic status or alignment that an entity held specifically during the Cold War period.
-
E.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.