Triple
T28446851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Summer Paralympics |
E715861
|
entity |
| Predicate | firstParalympicsInHostCountry |
P201746
|
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, firstParalympicsInHostCountry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstParalympicsInHostCountry Context triple: [2016 Summer Paralympics, firstParalympicsInHostCountry, true]
-
A.
ParalympicMovementStartedWith
Indicates that one entity marks the origin or initial beginning of the Paralympic movement in relation to another entity.
-
B.
introducedAsParalympicSport
Indicates that a sport was officially added to and recognized within the Paralympic Games program.
-
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.
paralympicHostCity
Indicates that a city has been selected to host a particular edition of the Paralympic Games.
-
E.
firstTimeCountryHostedSummerGames
Indicates that this was the first occasion on which a given country hosted the Summer Olympic Games.
- 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_6a001adc8c108190ab3a43f6415e2be3 |
completed | May 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a001a290330819097c2c3123f9014b4 |
completed | May 10, 2026, 5:39 a.m. |
| PDg | Predicate description generation | batch_6a001adbe6588190b7af521508b18898 |
completed | May 10, 2026, 5:42 a.m. |
Created at: April 28, 2026, 1:49 a.m.