Triple
T10958514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merdeka 118 |
E258905
|
entity |
| Predicate | estimatedOpeningYear |
P85309
|
FINISHED |
| Object | 2024 |
—
|
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: 2024 | Statement: [Merdeka 118, estimatedOpeningYear, 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedOpeningYear Context triple: [Merdeka 118, estimatedOpeningYear, 2024]
-
A.
officialOpeningYear
Indicates the calendar year in which something was formally opened or inaugurated for official use.
-
B.
originalPlannedOpeningYear
Indicates the year that was initially scheduled or intended for something to open, before any delays or changes.
-
C.
yearOpenedToPublic
Indicates the calendar year in which something (such as a place, facility, or service) was first made accessible to the general public.
-
D.
openingDateApproximate
chosen
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
E.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77126d9288190aa5daf2ba83d731d |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.