Triple
T32057304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy Cohn |
E818653
|
entity |
| Predicate | movementDisabilityContext |
P60789
|
FINISHED |
| Object | uses a wheelchair for sport |
—
|
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: uses a wheelchair for sport | Statement: [Andy Cohn, movementDisabilityContext, uses a wheelchair for sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementDisabilityContext Context triple: [Andy Cohn, movementDisabilityContext, uses a wheelchair for sport]
-
A.
disability
Indicates that an entity has a physical, mental, or sensory impairment that substantially limits one or more major life activities.
-
B.
causeOfDisability
Indicates that one entity is the reason or source that brings about another entity’s disability.
-
C.
disabilityCategories
Indicates that there is a relationship specifying which disability category or categories are associated with a given entity.
-
D.
usesWheelchair
chosen
Indicates that an entity relies on or operates a wheelchair for mobility or transportation.
-
E.
movementCapability
Indicates the ability or potential of an entity to move or be moved in a particular way or under certain conditions.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 12:21 a.m.