Triple
T25592950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gold Coast 2018 opening ceremony |
E641570
|
entity |
| Predicate | sportDisciplineScope |
P159459
|
FINISHED |
| Object | multi-sport |
—
|
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: multi-sport | Statement: [Gold Coast 2018 opening ceremony, sportDisciplineScope, multi-sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportDisciplineScope Context triple: [Gold Coast 2018 opening ceremony, sportDisciplineScope, multi-sport]
-
A.
WorldCupDiscipline
Indicates a disciplinary action (such as a card, suspension, or sanction) imposed on an entity in the context of a FIFA World Cup competition.
-
B.
sportTypeGoverned
Indicates that a governing body or organization has regulatory authority over a particular type of sport.
-
C.
sportsDisciplineSupported
Indicates that an entity provides support for, sponsors, or otherwise backs a particular sports discipline.
-
D.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
-
E.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
- 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_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 21, 2026, 4:25 p.m.