Triple
T18822931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo 2030 |
E460308
|
entity |
| Predicate | openingMonth |
P93895
|
FINISHED |
| Object | October 2030 |
—
|
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: October 2030 | Statement: [Expo 2030, openingMonth, October 2030]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMonth Context triple: [Expo 2030, openingMonth, October 2030]
-
A.
typicallyOpenFromMonth
chosen
Indicates the month from which something (such as a place, service, or facility) is usually open or begins operating.
-
B.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
C.
openingSeason
Indicates that an entity marks the beginning or first season of another entity, such as a series, event, or competition.
-
D.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
E.
openingForSeason
Indicates the event or action of beginning a new operational or active season for something (such as a venue, activity, or service).
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6bbc7148190819252071a765975 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.