Triple
T5294601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Para Games |
E119822
|
entity |
| Predicate | paralympicMovement |
P8641
|
FINISHED |
| Object | part of Paralympic movement |
—
|
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: part of Paralympic movement | Statement: [Asian Para Games, paralympicMovement, part of Paralympic movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paralympicMovement Context triple: [Asian Para Games, paralympicMovement, part of Paralympic movement]
-
A.
paralympics
chosen
Indicates that an entity is associated with, participates in, or is otherwise involved in the Paralympic Games or Paralympic movement.
-
B.
hasParalympicFunction
Indicates that an entity serves a specific role, duty, or function within the context of the Paralympic Games or Paralympic movement.
-
C.
paralympicsFollowed
Indicates that one Paralympic Games event chronologically follows another in sequence.
-
D.
paralympicsYear
Indicates the specific year in which a given edition of the Paralympic Games takes place.
-
E.
featuredParaSports
Indicates that an entity prominently presented or highlighted para sports or para-athletes, typically as a main focus in coverage, programming, or events.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.