Triple
T28945533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DUN Perak |
E730566
|
entity |
| Predicate | electionsHeldConcurrentlyWith |
P112700
|
FINISHED |
| Object | Malaysian general elections (usually) |
—
|
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: Malaysian general elections (usually) | Statement: [DUN Perak, electionsHeldConcurrentlyWith, Malaysian general elections (usually)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionsHeldConcurrentlyWith Context triple: [DUN Perak, electionsHeldConcurrentlyWith, Malaysian general elections (usually)]
-
A.
electionsHeldOnSameDayAs
chosen
Indicates that two elections took place on the exact same calendar day.
-
B.
electionsHeldOn
Indicates that one or more elections took place on a specified date or set of dates.
-
C.
electionHeldIn
Indicates that an election event took place within a specific geographic or political location.
-
D.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
-
E.
houseElectionsHeld
Indicates that elections have been conducted to choose members of a legislative house or lower chamber.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 8:40 a.m.