Triple
T29523190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valor da Vida |
E748990
|
entity |
| Predicate | featuresNarrativeElement |
P35676
|
FINISHED |
| Object | amnesia |
—
|
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: amnesia | Statement: [Valor da Vida, featuresNarrativeElement, amnesia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNarrativeElement Context triple: [Valor da Vida, featuresNarrativeElement, amnesia]
-
A.
narrativeCharacteristic
Indicates that one entity serves as a descriptive or defining narrative feature or quality of another entity.
-
B.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
D.
featuresFictionalElement
Indicates that one entity includes, presents, or incorporates a fictional element (such as an imaginary character, place, object, or concept) as part of its content or composition.
-
E.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: April 28, 2026, 4:43 p.m.