Triple
T5985545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triple Intervention |
E133216
|
entity |
| Predicate | underlyingMotive |
P6699
|
FINISHED |
| Object | Russian interest in Manchuria |
—
|
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: Russian interest in Manchuria | Statement: [Triple Intervention, underlyingMotive, Russian interest in Manchuria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingMotive Context triple: [Triple Intervention, underlyingMotive, Russian interest in Manchuria]
-
A.
motive
chosen
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
B.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
-
C.
openingMotive
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
-
D.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
E.
underpins
Indicates that one entity serves as the fundamental basis, support, or justification for another.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6dcaf08190bac27c7042e65e07 |
completed | March 22, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.