Triple
T23406065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Union |
E559936
|
entity |
| Predicate | providedEconomicAidTo |
P152137
|
FINISHED |
| Object | Mongolia |
—
|
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: Mongolia | Statement: [Soviet Union, providedEconomicAidTo, Mongolia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedEconomicAidTo Context triple: [Soviet Union, providedEconomicAidTo, Mongolia]
-
A.
providedMilitaryAidTo
Indicates that one entity has supplied military assistance, such as weapons, training, funding, or logistical support, to another entity.
-
B.
receivesMilitaryAidFrom
Indicates that one entity obtains military assistance, such as equipment, training, or funding, from another entity.
-
C.
diplomaticSupportFrom
Indicates that one entity provides diplomatic backing, advocacy, or assistance to another in international or political affairs.
-
D.
benefitedCountry
Indicates that one country gains an advantage, profit, or positive outcome from an action, event, or entity associated with another.
-
E.
isLinkedEconomicallyTo
Indicates that two entities are connected through economic relationships such as trade, investment, financial flows, or shared market dependencies.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4e364548190b98dc09240fba58e |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:38 p.m.