Triple
T12004712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom and Gloom |
E285751
|
entity |
| Predicate | isNewTrackOn |
P102621
|
FINISHED |
| Object | GRRR! |
—
|
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: GRRR! | Statement: [Doom and Gloom, isNewTrackOn, GRRR!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNewTrackOn Context triple: [Doom and Gloom, isNewTrackOn, GRRR!]
-
A.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
B.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
-
C.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
D.
isTrackEvent
Indicates that an event is classified as a track-related occurrence, such as a specific action or interaction being recorded for tracking or analytics purposes.
-
E.
nonAlbumTrack
Indicates that a track is not part of any official album release.
- F. None of above. chosen
Provenance (4 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c481a48190b311d6809808ef1b |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d9038e39f881908c58c19802ba2eb0 |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.