Triple
T18567749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 東久邇宮内閣 |
E453797
|
entity |
| Predicate | jurisdictionStartContext |
P126994
|
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: [東久邇宮内閣, jurisdictionStartContext, 日本の無条件降伏直後]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jurisdictionStartContext Context triple: [東久邇宮内閣, jurisdictionStartContext, 日本の無条件降伏直後]
-
A.
jurisdictionStartEvent
chosen
Indicates the event or point in time at which a particular jurisdiction or legal authority over something begins.
-
B.
hasJurisdictionContext
Indicates that a particular legal or regulatory authority, scope, or domain applies to or governs the referenced relationship or action.
-
C.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
D.
jurisdictionBasis
Indicates the legal grounds or authority under which one entity has the right to exercise jurisdiction over another entity, action, or matter.
-
E.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53affc3e08190b4d16b5ccb0bddbc |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.