Triple
T20928512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slow Man |
E515406
|
entity |
| Predicate | protagonistDisability |
P21469
|
FINISHED |
| Object | leg amputation |
—
|
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: leg amputation | Statement: [Slow Man, protagonistDisability, leg amputation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistDisability Context triple: [Slow Man, protagonistDisability, leg amputation]
-
A.
portraysCharacterWithDisability
Indicates that an entity depicts or represents a character who has a disability.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
protagonistMust
Indicates that a particular entity is required to serve as the main character or central focus within a narrative or scenario.
-
D.
protagonistCharacteristic
chosen
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
E.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f653a25c8190adb46f5d764afba7 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.