Triple
T30890539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Girl Without Hands |
E786884
|
entity |
| Predicate | protagonistOutcome |
P101514
|
FINISHED |
| Object | restoration |
—
|
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: restoration | Statement: [The Girl Without Hands, protagonistOutcome, restoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistOutcome Context triple: [The Girl Without Hands, protagonistOutcome, restoration]
-
A.
protagonistLoses
Indicates that the main character in a narrative is defeated, fails, or otherwise does not achieve their primary goal.
-
B.
characterArcOutcome
chosen
Indicates the resulting change, resolution, or final state of a character’s personal journey or development over the course of a narrative.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
protagonistReaction
Indicates how a main character responds emotionally or behaviorally to a particular event, situation, or stimulus.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:49 p.m.