Triple
T14861343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Fox |
E349498
|
entity |
| Predicate | usedProsthesis |
P54723
|
FINISHED |
| Object | artificial right leg |
—
|
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: artificial right leg | Statement: [Terry Fox, usedProsthesis, artificial right leg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProsthesis Context triple: [Terry Fox, usedProsthesis, artificial right leg]
-
A.
hasProsthesis
chosen
Indicates that an entity possesses or is equipped with an artificial substitute for a missing or impaired body part.
-
B.
usesProstheticMakeup
Indicates that an entity employs artificial makeup effects or appliances to alter appearance, typically for performance or portrayal purposes.
-
C.
usedOver
Indicates that one entity has been utilized, applied, or consumed in relation to another entity, typically as a resource, medium, or tool in a particular context or period.
-
D.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
E.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.