Triple
T33739243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Self-Righteous Brothers |
E864513
|
entity |
| Predicate | hasTypeOfDialogue |
P31437
|
FINISHED |
| Object | ranting monologues |
—
|
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: ranting monologues | Statement: [The Self-Righteous Brothers, hasTypeOfDialogue, ranting monologues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDialogue Context triple: [The Self-Righteous Brothers, hasTypeOfDialogue, ranting monologues]
-
A.
hasDialogueFunction
Indicates that an utterance or segment of discourse serves a specific communicative role or function within a dialogue (e.g., question, answer, request, acknowledgment).
-
B.
hasDialogueTrait
Indicates that an entity possesses a specific characteristic or quality related to dialogue or conversational behavior.
-
C.
hasDialogueIn
Indicates that an entity participates in or contains spoken or written dialogue within a specified context, such as a scene, work, or medium.
-
D.
hasDialogueSystem
Indicates that an entity includes or is equipped with a system for managing dialogue or conversational interactions.
-
E.
dialogueType
chosen
Indicates the specific kind or category of dialogue occurring between entities (e.g., question-answer, negotiation, instruction).
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:44 a.m.