Triple
T25592955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Coast 2018 opening ceremony |
E641570
|
entity |
| Predicate | isOpeningFor |
P158880
|
FINISHED |
| Object | Gold Coast 2018 closing ceremony |
—
|
NE NERFINISHED |
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: Gold Coast 2018 closing ceremony | Statement: [Gold Coast 2018 opening ceremony, isOpeningFor, Gold Coast 2018 closing ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOpeningFor Context triple: [Gold Coast 2018 opening ceremony, isOpeningFor, Gold Coast 2018 closing ceremony]
-
A.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
B.
isOpenTo
Indicates that one entity is receptive, willing, or available to consider, accept, or engage with another entity or proposal.
-
C.
seasonOpeningOrClosing
Indicates that an event marks either the beginning or the end of a particular season.
-
D.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
E.
isOpeningNumberOf
Indicates that something serves as the first or initial item in the numbered sequence of another entity.
- F. None of above. chosen
Provenance (4 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96ed2188190b4cb38ecb335b677 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:25 p.m.