Triple
T19871673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Geneva Motor Show |
E477530
|
entity |
| Predicate | openingPressDaysStart |
P30383
|
FINISHED |
| Object | 2018-03-06 |
—
|
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-03-06 | Statement: [2018 Geneva Motor Show, openingPressDaysStart, 2018-03-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingPressDaysStart Context triple: [2018 Geneva Motor Show, openingPressDaysStart, 2018-03-06]
-
A.
openingDay
Indicates the specific day on which something, typically an event, season, or venue, officially begins or first opens to the public.
-
B.
openingPublication
Indicates that an entity is the initial or first publication in which another entity (such as a work, concept, or result) was formally made public.
-
C.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
D.
openingDateLineC
Indicates the calendar date on which entity C is opened, initiated, or begins operation.
-
E.
openedAt
chosen
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d826f88190be04188997952d1b |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.