Triple
T34891102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bursa Malaysia |
E1006286
|
entity |
| Predicate | hasDerivativeProduct |
P98767
|
FINISHED |
| Object | crude palm oil futures |
—
|
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: crude palm oil futures | Statement: [Bursa Malaysia, hasDerivativeProduct, crude palm oil futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivativeProduct Context triple: [Bursa Malaysia, hasDerivativeProduct, crude palm oil futures]
-
A.
hasDerivatives
Indicates that one entity is derived, obtained, or developed from another entity.
-
B.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
C.
hasDerivativesBasedOnIt
Indicates that one entity serves as the basis or source from which one or more derivative entities are created or derived.
-
D.
hasDerivativeUse
Indicates that one entity is used as a basis, source, or component for creating or enabling another entity or function.
-
E.
hasDerivativesListedOn
chosen
Indicates that financial derivative instruments based on an underlying asset or entity are listed and traded on a specified exchange or trading venue.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4 p.m.