Triple
T25082467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahli Dewan Undangan Negeri |
E628220
|
entity |
| Predicate | eligibleCandidate |
P21353
|
FINISHED |
| Object | Malaysian citizen |
—
|
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: Malaysian citizen | Statement: [Ahli Dewan Undangan Negeri, eligibleCandidate, Malaysian citizen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleCandidate Context triple: [Ahli Dewan Undangan Negeri, eligibleCandidate, Malaysian citizen]
-
A.
candidateFor
Indicates that one entity is being considered or proposed as a possible choice, option, or selection for another entity (such as a role, position, or outcome).
-
B.
supportedCandidateInElection
Indicates that one entity endorsed or backed another entity as a candidate in a specific election.
-
C.
isCandidate
Indicates that an entity is being considered or put forward for a particular position, role, or selection process.
-
D.
featuredCandidate
Indicates that a particular candidate is highlighted or given special prominence relative to others.
-
E.
eligibleAppointees
chosen
Indicates that certain individuals or entities meet the required criteria to be considered for a particular appointment or position.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:22 a.m.