Triple
T28446852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Summer Paralympics |
E715861
|
entity |
| Predicate | firstParalympicsInSouthAmerica |
P201760
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2016 Summer Paralympics, firstParalympicsInSouthAmerica, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstParalympicsInSouthAmerica Context triple: [2016 Summer Paralympics, firstParalympicsInSouthAmerica, true]
-
A.
firstParalympicsInHostCountry
Indicates that the Paralympic Games were held for the first time in the specified host country.
-
B.
ParalympicMovementStartedWith
Indicates that one entity marks the origin or initial beginning of the Paralympic movement in relation to another entity.
-
C.
introducedAsParalympicSport
Indicates that a sport was officially added to and recognized within the Paralympic Games program.
-
D.
hostedParapanAmericanGames
Indicates that a location or entity served as the host for the Parapan American Games event.
-
E.
paralympics
Indicates that an entity is associated with, participates in, or is otherwise involved in 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
| PDg | Predicate description generation | batch_6a001cc053ac8190927768a4ecb023b9 |
completed | May 10, 2026, 5:50 a.m. |
Created at: April 28, 2026, 1:49 a.m.