Triple
T32223592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Dodson |
E823133
|
entity |
| Predicate | ParalympicCity |
P80054
|
FINISHED |
| Object | Rio de Janeiro |
—
|
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: Rio de Janeiro | Statement: [Richard Dodson, ParalympicCity, Rio de Janeiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ParalympicCity Context triple: [Richard Dodson, ParalympicCity, Rio de Janeiro]
-
A.
paralympicHostCity
chosen
Indicates that a city has been selected to host a particular edition of the Paralympic Games.
-
B.
paralympicCounterpartOf
Indicates that one entity is the corresponding Paralympic version or equivalent of another entity, typically an Olympic event, sport, or competition.
-
C.
ParalympicSportHosted
Indicates that a particular Paralympic sport was held or staged as part of a specific edition of the Paralympic Games at a given host location.
-
D.
paralympicVenueFor
Indicates that a venue is designated or used as the location for hosting Paralympic events or competitions.
-
E.
paralympicGamesEdition
Indicates the specific edition of the Paralympic Games in which an entity (such as an athlete, event, or result) is involved or to which it is related.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbc8c6c881908ce99e774c010ff5 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:38 a.m.