Triple
T15191986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Exposure |
E363037
|
entity |
| Predicate | hasTrackFeature |
P115884
|
FINISHED |
| Object | guitar solos |
—
|
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: guitar solos | Statement: [Double Exposure, hasTrackFeature, guitar solos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackFeature Context triple: [Double Exposure, hasTrackFeature, guitar solos]
-
A.
hasTrackFeatures
chosen
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasTrackSection
Indicates that an entity includes, is composed of, or is associated with a specific section or segment of a track.
-
D.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
E.
hasTrackSurface
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067d55ac8190b7a7fce36e6ddf3c |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:10 a.m.