Triple
T9905019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memories (Part II) |
E184983
|
entity |
| Predicate | featuresNarrativeVoice |
P5869
|
FINISHED |
| Object | first person |
—
|
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: first person | Statement: [Memories (Part II), featuresNarrativeVoice, first person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresNarrativeVoice Context triple: [Memories (Part II), featuresNarrativeVoice, first person]
-
A.
narrativeCharacteristic
Indicates that one entity serves as a descriptive or defining narrative feature or quality of another entity.
-
B.
settingOfNarration
Indicates the place, time, or context in which a narrated event or story takes place.
-
C.
narratorType
Indicates the narrative perspective or role from which a story or account is being told.
-
D.
narrativeStyle
chosen
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
E.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
- 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_69ca8296165881908ca4750701af1f29 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb4e641e881909dfba78fcb96c433 |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.