Triple
T30890535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Girl Without Hands |
E786884
|
entity |
| Predicate | protagonistLoses |
P176345
|
FINISHED |
| Object | her hands |
—
|
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: her hands | Statement: [The Girl Without Hands, protagonistLoses, her hands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistLoses Context triple: [The Girl Without Hands, protagonistLoses, her hands]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
protagonistConfronts
Indicates that a main character directly faces and challenges another character, force, or problem in a conflictual encounter.
-
C.
loserTitle
Indicates the title, label, or designation assigned to the losing party in a competition, contest, or comparison.
-
D.
finalDefeatIn
Indicates that one entity experiences its ultimate or conclusive defeat within a specified event, context, or location.
-
E.
protagonistAction
Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
- F. None of above. chosen
Provenance (4 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 29, 2026, 8:49 p.m.