Triple
T29650100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DUN Kedah |
E750111
|
entity |
| Predicate | membersChosenBy |
P53317
|
FINISHED |
| Object | state elections in Kedah |
—
|
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: state elections in Kedah | Statement: [DUN Kedah, membersChosenBy, state elections in Kedah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: membersChosenBy Context triple: [DUN Kedah, membersChosenBy, state elections in Kedah]
-
A.
membersDrawnFrom
Indicates that the members of one group, set, or collection are selected or sourced from another group, set, or collection.
-
B.
membersAppointedFor
Indicates that certain individuals are formally designated to serve as members for a specific body, role, or purpose.
-
C.
selectsMembersBy
Indicates that an entity chooses or designates specific members from a larger group or collection based on some criteria.
-
D.
membersAreAppointedIn
Indicates that the members of a group or body are selected or assigned to their positions within a particular organization, institution, or context.
-
E.
membersElected
chosen
Indicates that certain individuals are chosen through an election process to serve as members of a group, body, or organization.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 6:52 p.m.