Triple
T34891080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bursa Malaysia |
E1006286
|
entity |
| Predicate | marketIndex |
P10508
|
FINISHED |
| Object | FTSE Bursa Malaysia KLCI |
—
|
NE NERFINISHED |
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: FTSE Bursa Malaysia KLCI | Statement: [Bursa Malaysia, marketIndex, FTSE Bursa Malaysia KLCI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketIndex Context triple: [Bursa Malaysia, marketIndex, FTSE Bursa Malaysia KLCI]
-
A.
stockIndex
chosen
Indicates a relationship where a stock market index tracks or represents the aggregated performance of a selected group of stocks.
-
B.
marketStatus
Indicates the current trading or availability condition of an asset, product, or market (e.g., open, closed, active, suspended).
-
C.
sharesMarket
Indicates that two entities operate within or target the same market or customer segment.
-
D.
marketCenter
Indicates a relationship where a location functions as a central place for commercial exchange, trade, or economic activity for a surrounding area.
-
E.
marketsIn
Indicates that one entity promotes, sells, or offers another entity’s products or services within a particular market or geographic area.
- 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_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.