Triple
T18219844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easy Listening |
E436262
|
entity |
| Predicate | avoidsCharacteristic |
P92600
|
FINISHED |
| Object | aggressive rhythms |
—
|
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: aggressive rhythms | Statement: [Easy Listening, avoidsCharacteristic, aggressive rhythms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidsCharacteristic Context triple: [Easy Listening, avoidsCharacteristic, aggressive rhythms]
-
A.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
B.
seeksToAvoid
chosen
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
C.
avoidsColorsOf
Indicates that one entity deliberately refrains from using, displaying, or interacting with the colors associated with another entity.
-
D.
maskCharacteristic
Indicates that one entity serves to conceal, obscure, or alter the apparent characteristics or properties of another entity.
-
E.
mustAvoid
Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47a3b1c8190919e954089b41ae0 |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.