Triple
T19023712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barisan Nasional |
E465551
|
entity |
| Predicate | heldFederalPowerUntil |
P133596
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Barisan Nasional, heldFederalPowerUntil, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldFederalPowerUntil Context triple: [Barisan Nasional, heldFederalPowerUntil, 2018]
-
A.
heldExecutivePowerUntil
Indicates that an entity exercised executive authority or leadership in a role or office up to a specified end date or point in time.
-
B.
servedAsConstitutionUntil
Indicates that one document functioned as the official constitution of an entity up to a specified point in time.
-
C.
federalPartCameIntoForce
Indicates that a specific part of a federal law or regulation has officially taken legal effect from a certain point in time.
-
D.
hasTemporalJurisdictionFrom
Indicates that an authority’s jurisdiction or control over something begins at a specified point in time.
-
E.
effectOnFederalPower
Indicates how an action, decision, or condition changes, limits, or expands the authority or powers of the federal government.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6e166088190937ef19739437f7c |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8f6f7c8190af645bf08823ee2b |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:02 p.m.