Triple
T13794761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawn FM |
E331486
|
entity |
| Predicate | narrativeFramework |
P7324
|
FINISHED |
| Object | fictional radio station |
—
|
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: fictional radio station | Statement: [Dawn FM, narrativeFramework, fictional radio station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeFramework Context triple: [Dawn FM, narrativeFramework, fictional radio station]
-
A.
narrativeFrame
chosen
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
C.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
D.
narrativeFormat
Indicates the specific structural or stylistic form in which a narrative is presented or expressed.
-
E.
narrativeConcept
Indicates a conceptual or thematic element within a narrative, such as an idea, motif, or organizing principle that shapes the story’s structure or meaning.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0259b0e4819081c11ced694384fb |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.