Triple
T1488190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Japan |
E29515
|
entity |
| Predicate | executivePower |
P23177
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Emperor of Japan, executivePower, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executivePower Context triple: [Emperor of Japan, executivePower, no]
-
A.
retainedExecutivePowerFor
Indicates that an entity has kept or reserved executive authority or decision-making power for another entity or context, rather than delegating or relinquishing it.
-
B.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
C.
hadExecutivePowerIn
chosen
Indicates that an entity held executive authority or governing power within a specified organization, institution, or jurisdiction during a certain period.
-
D.
executiveBody
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
E.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a44efc819084254614d8ea4669 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.