Triple
T2102952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exposure |
E37130
|
entity |
| Predicate | firstPersonNarration |
P1924
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Exposure, firstPersonNarration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPersonNarration Context triple: [Exposure, firstPersonNarration, yes]
-
A.
narrativePerspective
chosen
Indicates the point of view or vantage from which a narrative is told, specifying the relationship between the storyteller and the events being described.
-
B.
narrativeType
Indicates the specific kind or category of narrative (e.g., genre, structural form, or storytelling mode) associated with an entity.
-
C.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
D.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
-
E.
fictionalNarrator
Indicates that one entity serves as the narrator or storytelling voice within a fictional work that features the other entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabe1e9081908ea66c5406e2f1d9 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.