Triple
T1442596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2018 Commonwealth Games |
E31106
|
entity |
| Predicate | includedParaSports |
P15646
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2018 Commonwealth Games, includedParaSports, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedParaSports Context triple: [2018 Commonwealth Games, includedParaSports, yes]
-
A.
paralympics
Indicates that an entity is associated with, participates in, or is otherwise involved in the Paralympic Games or Paralympic movement.
-
B.
includesParalympicDivision
chosen
Indicates that an entity (such as a sport, event, or competition) has a designated division or category specifically for Paralympic or para-athlete participation.
-
C.
wheelchairEventsIncluded
Indicates that the specified events explicitly include or accommodate the use of wheelchairs.
-
D.
hasParalympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Paralympic Games or Paralympic movement.
-
E.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
- 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c55714588190a95b4f677c21cbaa |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.