Triple
T22287640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevation (Tomb Raider Mix) |
E550904
|
entity |
| Predicate | hasCinematicSound |
P92004
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Elevation (Tomb Raider Mix), hasCinematicSound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCinematicSound Context triple: [Elevation (Tomb Raider Mix), hasCinematicSound, true]
-
A.
hasCinematicFeature
Indicates that something possesses a specific cinematic characteristic, quality, or element related to film or visual storytelling.
-
B.
hasSoundMix
Indicates that one entity uses, features, or is associated with a particular sound mix configuration or audio mixing format.
-
C.
isSoundFilm
Indicates that a film includes synchronized recorded sound as an integral part of its presentation, rather than being a silent film.
-
D.
hasSoundtrackCharacteristic
chosen
Indicates that a soundtrack possesses a specified quality, feature, or attribute.
-
E.
hasSoundStages
Indicates that one entity possesses, contains, or is equipped with sound stages used for audio and film/TV production.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560896348190985725ac8ad406b3 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.