Triple
T32548472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Economy of Burundi |
E831907
|
entity |
| Predicate | hasKeyImport |
P184403
|
FINISHED |
| Object | petroleum products |
—
|
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: petroleum products | Statement: [Economy of Burundi, hasKeyImport, petroleum products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyImport Context triple: [Economy of Burundi, hasKeyImport, petroleum products]
-
A.
hasKeyPass
Indicates that an entity possesses or is granted a key-based pass that allows access or authorization to something.
-
B.
hasKeyInfrastructure
Indicates that an entity possesses or is associated with essential infrastructure components critical for its operation or function.
-
C.
hasKeyMaterial
Indicates that an entity possesses or contains the cryptographic key material required for encryption, decryption, or related security operations.
-
D.
hasKeyImage
Indicates that one entity is designated as the primary or representative image associated with another entity.
-
E.
hasKeyStrength
Indicates that an entity possesses a primary or defining strength, capability, or advantage.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: May 1, 2026, 1:02 a.m.