Triple
T30094097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan Colombia |
E764814
|
entity |
| Predicate | approximateUSFunding |
P195083
|
FINISHED |
| Object | over 10 billion US dollars |
—
|
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: over 10 billion US dollars | Statement: [Plan Colombia, approximateUSFunding, over 10 billion US dollars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateUSFunding Context triple: [Plan Colombia, approximateUSFunding, over 10 billion US dollars]
-
A.
approximateFundsRaised
Indicates an estimated amount of money that has been raised, rather than an exact or final total.
-
B.
peakAnnualFunding
Indicates the maximum amount of funding an entity receives in a single year within a given period.
-
C.
fundingLevel
Indicates the amount or degree of financial resources allocated or committed to an entity, project, or activity.
-
D.
fundFinancedBy
Indicates that a particular fund receives its financial resources or backing from a specified source or entity.
-
E.
fundingFocus
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
| PDg | Predicate description generation | batch_69fda4fe67a08190bdaa84ceabd6de6c |
completed | May 8, 2026, 8:55 a.m. |
Created at: April 29, 2026, 7:06 p.m.