Triple
T8932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truman Doctrine |
E178
|
entity |
| Predicate | aidAmount |
P432
|
FINISHED |
| Object | 400 million U.S. dollars to Greece and Turkey |
—
|
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: 400 million U.S. dollars to Greece and Turkey | Statement: [Truman Doctrine, aidAmount, 400 million U.S. dollars to Greece and Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aidAmount Context triple: [Truman Doctrine, aidAmount, 400 million U.S. dollars to Greece and Turkey]
-
A.
totalAidAmountUSD
chosen
Indicates the total monetary value of aid provided, expressed in U.S. dollars.
-
B.
totalAidAmountAdjusted
Indicates the total amount of aid provided, after applying any relevant adjustments such as corrections, discounts, or recalculations.
-
C.
donated
Indicates that one entity voluntarily gave something of value (such as money, goods, or time) to another entity, typically without expecting anything in return.
-
D.
monetaryValueSponsor
Indicates that a sponsor provides or assigns a specific monetary value (amount of funding) to another entity or activity.
-
E.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23fe52ec48190a4d24101c91434ed |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.