Triple
T11207131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavin Cavanagh |
E265197
|
entity |
| Predicate | narrativeSettingContext |
P45019
|
FINISHED |
| Object | pirate radio |
—
|
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: pirate radio | Statement: [Gavin Cavanagh, narrativeSettingContext, pirate radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeSettingContext Context triple: [Gavin Cavanagh, narrativeSettingContext, pirate radio]
-
A.
narrativeSettingOfWork
chosen
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
B.
narrativeRoleContext
Indicates the contextual narrative function or role an entity plays within a story or discourse (e.g., protagonist, antagonist, narrator) relative to other elements.
-
C.
locationOfNarrative
Indicates the place or setting where the events or story described in the narrative occur.
-
D.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.