Triple
T4603577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia and China |
E100375
|
entity |
| Predicate | armsTrade |
P57391
|
FINISHED |
| Object | Russian arms exports to China |
—
|
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 arms exports to China | Statement: [Russia and China, armsTrade, Russian arms exports to China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armsTrade Context triple: [Russia and China, armsTrade, Russian arms exports to China]
-
A.
armamentWartime
Indicates a relationship where an entity serves as a weapon or military equipment used by another entity specifically in a wartime context.
-
B.
nuclearWeaponsState
Indicates that a state possesses, has developed, or is recognized as having nuclear weapons capabilities.
-
C.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
E.
claimedDecommissioningOfWeapons
Indicates that an entity has asserted or reported that certain weapons have been taken out of service or rendered non-operational.
- F. None of above. chosen
Provenance (4 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5975ec688190839bd22669343a76 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.