Triple

T22622622
Position Surface form Disambiguated ID Type / Status
Subject U.S. Paralympic Team E558324 entity
Predicate hasDisabilityCategories P63365 FINISHED
Object physical impairments 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: physical impairments | Statement: [U.S. Paralympic Team, hasDisabilityCategories, physical impairments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDisabilityCategories
Context triple: [U.S. Paralympic Team, hasDisabilityCategories, physical impairments]
  • A. disabilityCategories chosen
    Indicates that there is a relationship specifying which disability category or categories are associated with a given entity.
  • B. hasDisabilityRepresentation
    Indicates that something includes, portrays, or accounts for the presence and experiences of people with disabilities.
  • 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. disability
    Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
  • 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_69e24545a8e08190bfa7482a2c725ff1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f16e3ad6f48190b351a52e4b1d9b2d completed April 29, 2026, 2:34 a.m.
PD Predicate disambiguation batch_69ee62855558819080da946c7b35a160 completed April 26, 2026, 7:07 p.m.
Created at: April 17, 2026, 3 p.m.