Triple
T20013107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The experiences of Adrian Cronauer |
E494637
|
entity |
| Predicate | roleOfProtagonist |
P20969
|
FINISHED |
| Object | radio DJ |
—
|
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: radio DJ | Statement: [The experiences of Adrian Cronauer, roleOfProtagonist, radio DJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfProtagonist Context triple: [The experiences of Adrian Cronauer, roleOfProtagonist, radio DJ]
-
A.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
B.
protagonistType
chosen
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
protagonistDescription
Indicates that a text provides a descriptive summary or characterization of the story’s main protagonist.
-
D.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
E.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66238f434819083b11458179bb601 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.