Triple
T34891070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bursa Malaysia |
E1006286
|
entity |
| Predicate | secondaryBoard |
P199330
|
FINISHED |
| Object | ACE Market |
—
|
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: ACE Market | Statement: [Bursa Malaysia, secondaryBoard, ACE Market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryBoard Context triple: [Bursa Malaysia, secondaryBoard, ACE Market]
-
A.
secondaryLevelOfEducation
Indicates that an entity has completed, is enrolled in, or is otherwise associated with secondary-level (high school or equivalent) education.
-
B.
secondaryStages
Indicates that one or more stages occur as subsequent or follow-up phases relative to an initial or primary stage in a process or sequence.
-
C.
secondaryCampus
Indicates that an institution or organization has an additional, non-primary campus located at a different site.
-
D.
secondarySingle
Indicates that an entity serves as a secondary, but singular, counterpart or role in relation to another primary entity.
-
E.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4 p.m.