Triple
T13751951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Arena |
E330373
|
entity |
| Predicate | ParalympicSportHosted |
P110835
|
FINISHED |
| Object | wheelchair basketball |
—
|
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: wheelchair basketball | Statement: [Wembley Arena, ParalympicSportHosted, wheelchair basketball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ParalympicSportHosted Context triple: [Wembley Arena, ParalympicSportHosted, wheelchair basketball]
-
A.
paralympicHostCity
Indicates that a city has been selected to host a particular edition of the Paralympic Games.
-
B.
WinterParalympicEventHosted
Indicates that a specific location or organization served as the host for a particular Winter Paralympic event.
-
C.
paralympics
Indicates that an entity is associated with, participates in, or is otherwise involved in the Paralympic Games or Paralympic movement.
-
D.
olympicSportHosted
Indicates that a particular Olympic sport was held or staged at a specific Olympic Games or host location.
-
E.
hasParalympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Paralympic Games or Paralympic movement.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0215cfa08190aaed8b089aff217b |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:09 p.m.