Triple
T13782934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnie the Moocher |
E331173
|
entity |
| Predicate | hasRefrainType |
P62294
|
FINISHED |
| Object | audience participation refrain |
—
|
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: audience participation refrain | Statement: [Minnie the Moocher, hasRefrainType, audience participation refrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRefrainType Context triple: [Minnie the Moocher, hasRefrainType, audience participation refrain]
-
A.
refrainStructure
Indicates a structural relationship where a recurring refrain section is organized, positioned, or patterned within a larger composition or sequence.
-
B.
refrainCount
Indicates the number of times a particular refrain or repeated segment occurs within a larger sequence or structure.
-
C.
refrain
Indicates that an entity deliberately holds back from performing a particular action or behavior.
-
D.
refrainText
Indicates that a piece of text functions as the recurring refrain or repeated line within a larger work, such as a song or poem.
-
E.
hasChorusStyle
chosen
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
- 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_69de0247ccc881908dad7b547221f15d |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.