Triple
T26060320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Japan |
E657239
|
entity |
| Predicate | createdPuppetState |
P145621
|
FINISHED |
| Object | Manchukuo |
—
|
NE NERFINISHED |
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: Manchukuo | Statement: [Imperial Japan, createdPuppetState, Manchukuo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPuppetState Context triple: [Imperial Japan, createdPuppetState, Manchukuo]
-
A.
stateCreated
chosen
Indicates that a state or governmental entity was brought into existence or formally established by another agent or process.
-
B.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
C.
createdPeer
Indicates that one entity brought another entity into existence or initiated its formation as a peer or counterpart.
-
D.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
-
E.
successorStatesCreated
Indicates that new subsequent or follow-up states have been generated from a given state or condition.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 7:16 p.m.