Triple
T22287641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevation (Tomb Raider Mix) |
E550904
|
entity |
| Predicate | hasRockDrivenSound |
P147698
|
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), hasRockDrivenSound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockDrivenSound Context triple: [Elevation (Tomb Raider Mix), hasRockDrivenSound, true]
-
A.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
C.
isRockSong
Indicates that the subject is a song belonging to the rock music genre.
-
D.
hasRockSubgenre
Indicates a relationship where one musical style is classified as a subgenre within the broader category of rock music.
-
E.
hasRockArchName
Indicates that a rock arch is associated with a specific name or designation.
- 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_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. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:40 p.m.