Triple
T3315217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mad Girl’s Love Song |
E69664
|
entity |
| Predicate | usesFirstPersonNarration |
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: [Mad Girl’s Love Song, usesFirstPersonNarration, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFirstPersonNarration Context triple: [Mad Girl’s Love Song, usesFirstPersonNarration, 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.
hasNarration
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
-
C.
narratorType
Indicates the narrative perspective or role from which a story or account is being told.
-
D.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
E.
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.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb110b28081909b366623e3b0783d |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.