Triple
T12647896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dewan Perwakilan Rakyat |
E302077
|
entity |
| Predicate | lastKnownNumberOfMembers |
P106175
|
FINISHED |
| Object | 575 members |
—
|
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: 575 members | Statement: [Dewan Perwakilan Rakyat, lastKnownNumberOfMembers, 575 members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastKnownNumberOfMembers Context triple: [Dewan Perwakilan Rakyat, lastKnownNumberOfMembers, 575 members]
-
A.
lastKnownMember
Indicates that the subject is the most recent or final identified member of a particular group, lineage, or set.
-
B.
previousNumberOfMembers
Indicates the number of members an entity had at an earlier or prior point in time.
-
C.
originalNumberOfMembers
Indicates the initial total count of members in a group or organization before any changes such as additions or removals.
-
D.
numberOfKnownMembers
Indicates the count of members within a group or set whose identities are known or have been explicitly determined.
-
E.
numberOfMembersDeterminedBy
Indicates that the quantity of members in one entity is defined or constrained by another entity or factor.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:17 p.m.