Triple
T832356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 2020 |
E17992
|
entity |
| Predicate | originalPlannedOpeningDate |
P4691
|
FINISHED |
| Object | 2020-10-20 |
—
|
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: 2020-10-20 | Statement: [Expo 2020, originalPlannedOpeningDate, 2020-10-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPlannedOpeningDate Context triple: [Expo 2020, originalPlannedOpeningDate, 2020-10-20]
-
A.
officialOpeningDate
Indicates the calendar date on which something is formally inaugurated or officially opened for use or operation.
-
B.
datePlanned
chosen
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
C.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
D.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
E.
originalPlannedLaunchYear
Indicates the year that was initially scheduled or intended for an entity’s launch before any delays or changes.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abb647988190950e1790bcfa60a5 |
completed | March 1, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7b3d2481909199f7c9f305bdfe |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.