Triple
T33445797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKTO |
E856494
|
entity |
| Predicate | hasNotableSongCharacteristic |
—
|
GENERATED |
| Object | catchy pop hooks |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSongCharacteristic Context triple: [MKTO, hasNotableSongCharacteristic, catchy pop hooks]
-
A.
notableSongCharacteristic
chosen
Indicates that a song is distinguished by a particular notable feature or quality, such as style, structure, or performance trait.
-
B.
hasNotableSongType
Indicates that an entity is associated with a specific type or category of notable song.
-
C.
hasSpecialSong
Indicates that one entity possesses or is associated with a particular song that is unique, distinctive, or specially designated for it.
-
D.
hasNotableSongNumber
Indicates that an entity is associated with a specific song identified by its notable number or index within a collection or sequence.
-
E.
hasNotableBeat
Indicates that an entity (such as a journalist or reporter) is professionally assigned to cover a specific topic, area, or subject as their primary reporting focus.
- F. None of above.
Provenance (1 batch)
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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.