Triple
T15905986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mondo |
E385716
|
entity |
| Predicate | definesToneOf |
P49759
|
FINISHED |
| Object | Good Vibes |
—
|
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: Good Vibes | Statement: [Mondo, definesToneOf, Good Vibes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesToneOf Context triple: [Mondo, definesToneOf, Good Vibes]
-
A.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
B.
contributesToTone
chosen
Indicates that one entity plays a role in shaping, influencing, or determining the overall tone or mood of another entity.
-
C.
tone
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
-
D.
supportsTone
Indicates that one entity is compatible with, enables, or can correctly handle a specified tone or tonal characteristic of another entity.
-
E.
tonal
Indicates that one entity has a tone, pitch pattern, or tonal quality in relation to another (such as a language, sound, or musical element).
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142ca3b208190946c3aa4c1e6087c |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:52 a.m.