Triple
T22336632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elevation (Influx Mix) |
E552163
|
entity |
| Predicate | hasAlternativeArrangement |
P147813
|
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 (Influx Mix), hasAlternativeArrangement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeArrangement Context triple: [Elevation (Influx Mix), hasAlternativeArrangement, true]
-
A.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
-
B.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
C.
hasAlternativeMedium
Indicates that an entity is available, expressed, or presented in another medium or format as an alternative to its primary one.
-
D.
hasLyricalVariant
Indicates that one item has an alternative version that differs in its lyrics while remaining related to the original.
-
E.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577f2f208190ac6270ac4581fa15 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
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:43 p.m.