Triple

T24284771
Position Surface form Disambiguated ID Type / Status
Subject 2015 IPC Athletics World Championships E605639 entity
Predicate hasDisabilityClassifications P63365 FINISHED
Object T11–T13 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: T11–T13 | Statement: [2015 IPC Athletics World Championships, hasDisabilityClassifications, T11–T13]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisabilityClassifications
Context triple: [2015 IPC Athletics World Championships, hasDisabilityClassifications, T11–T13]
  • A. hasDisabilityRepresentation
    Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
  • B. disabilityCategories chosen
    Indicates that there is a relationship specifying which disability category or categories are associated with a given entity.
  • C. causeOfDisability
    Indicates that one entity is the reason or source that brings about another entity’s disability.
  • D. hasAdaptationNeed
    Indicates that an entity requires some form of adaptation or adjustment to better suit specific conditions, contexts, or needs.
  • E. hasImpairmentStatus
    Indicates that an entity possesses a particular condition of functional limitation, disability, or impairment status.
  • 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_69e295480d0c8190846fc3c2e2da1d4c completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f28f54c5948190a28207d47d6205e4 completed April 29, 2026, 11:08 p.m.
PD Predicate disambiguation batch_69f1c457a2908190993824395b3c365d completed April 29, 2026, 8:41 a.m.
Created at: April 18, 2026, 12:08 a.m.