Triple
T22599707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aimee Mullins |
E574779
|
entity |
| Predicate | legsAmputated |
P53592
|
FINISHED |
| Object | both legs below the knee |
—
|
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: both legs below the knee | Statement: [Aimee Mullins, legsAmputated, both legs below the knee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legsAmputated Context triple: [Aimee Mullins, legsAmputated, both legs below the knee]
-
A.
lostLimb
chosen
Indicates that an entity has had one or more of its limbs removed or rendered permanently absent, typically as a result of injury, surgery, or trauma.
-
B.
numberOfLegsLost
Indicates the number of legs an entity has lost as a result of some event or condition.
-
C.
lostLimbTo
Indicates that one entity has had a limb removed, severed, or rendered nonfunctional as a direct result of another entity or cause.
-
D.
legs
Indicates that an entity possesses legs, specifying the presence or number of leg-like appendages associated with it.
-
E.
hasLimbs
Indicates that an entity possesses one or more limbs as physical appendages.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626b5f5481909a104088d1c96720 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:50 p.m.