Triple
T38629934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straight Shooting |
E937422
|
entity |
| Predicate | hasOriginalReleaseType |
P45770
|
FINISHED |
| Object | theatrical release |
—
|
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: theatrical release | Statement: [Straight Shooting, hasOriginalReleaseType, theatrical release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalReleaseType Context triple: [Straight Shooting, hasOriginalReleaseType, theatrical release]
-
A.
hasOriginalSongReleaseContext
Indicates that an original song is associated with a specific context in which it was first released (such as an event, medium, or setting).
-
B.
originalReleaseStatus
chosen
Indicates the publication or distribution state of a work at the time of its initial release.
-
C.
hasOriginalAlbumRelease
Indicates that an album or musical work is associated with its first official release instance or edition.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
hasOriginalProducer
Indicates that an entity was initially created, manufactured, or produced by a specific producer or organization.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:32 p.m.