Triple
T28212508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maverick franchise |
E711211
|
entity |
| Predicate | knownForTone |
P49759
|
FINISHED |
| Object | lighthearted |
—
|
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: lighthearted | Statement: [Maverick franchise, knownForTone, lighthearted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForTone Context triple: [Maverick franchise, knownForTone, lighthearted]
-
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.
notableSoundCharacteristic
Indicates a distinctive or noteworthy quality of the sound produced or associated with an entity.
-
D.
knownForMusicGenre
Indicates that an entity is recognized or notable for producing, performing, or being associated with a particular music genre.
-
E.
leadingTone
Indicates that one musical pitch functions as a leading tone, creating a strong tendency to resolve stepwise (typically upward) to a specific target pitch.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 10:40 p.m.