Triple
T32548443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Burundi |
E831907
|
entity |
| Predicate | isHeavilyDependentOn |
P1022
|
FINISHED |
| Object | foreign aid |
—
|
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: foreign aid | Statement: [Economy of Burundi, isHeavilyDependentOn, foreign aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHeavilyDependentOn Context triple: [Economy of Burundi, isHeavilyDependentOn, foreign aid]
-
A.
hasDependency
chosen
Indicates that one entity relies on or requires another entity in order to function, exist, or be fulfilled.
-
B.
isHistoricallyDependentOn
Indicates that one entity’s existence, development, or validity is contingent on prior events, conditions, or states associated with another entity in history.
-
C.
kernelDependsOn
Indicates that one kernel or core software component requires another kernel or component to be present or available in order to function correctly.
-
D.
hasDependentSupport
Indicates that one entity provides financial or material support for another entity who is recognized as a dependent.
-
E.
isKeyDependent
Indicates that one entity’s existence, validity, or identification depends on another entity’s key or primary identifier.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c3636c81908cb7b9418c47dbf0 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.