Triple
T8179285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jalur Gemilang |
E191017
|
entity |
| Predicate | officialNameAdoptedOn |
P3399
|
FINISHED |
| Object | 1997-08-31 |
—
|
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: 1997-08-31 | Statement: [Jalur Gemilang, officialNameAdoptedOn, 1997-08-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialNameAdoptedOn Context triple: [Jalur Gemilang, officialNameAdoptedOn, 1997-08-31]
-
A.
officialNameSince
Indicates the date or point in time from which a particular official name has been in effect for an entity.
-
B.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
C.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
D.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
E.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4abd9768819091298e4dd995ac96 |
completed | March 31, 2026, 4:17 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.