Triple
T9678027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run Devil Run |
E234208
|
entity |
| Predicate | recordingStyle |
P89583
|
FINISHED |
| Object | back-to-basics |
—
|
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: back-to-basics | Statement: [Run Devil Run, recordingStyle, back-to-basics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordingStyle Context triple: [Run Devil Run, recordingStyle, back-to-basics]
-
A.
recordingMethod
Indicates the technique or process used to capture or record something (such as data, audio, or video).
-
B.
recordingType
Indicates the specific kind or category of recording associated with an entity (e.g., audio, video, live, studio, etc.).
-
C.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
D.
recordedWith
Indicates that something was captured, documented, or produced using a particular tool, device, medium, or method.
-
E.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
- 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_69ca84c99e34819092e5563a7106cfca |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9c9b01708190aaf51cf4d36015a0 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:16 p.m.