Triple
T15789854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | By the Time I Get to Phoenix |
E382834
|
entity |
| Predicate | hasOrchestralArrangement |
P87307
|
FINISHED |
| Object | Isaac Hayes version |
—
|
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: Isaac Hayes version | Statement: [By the Time I Get to Phoenix, hasOrchestralArrangement, Isaac Hayes version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrchestralArrangement Context triple: [By the Time I Get to Phoenix, hasOrchestralArrangement, Isaac Hayes version]
-
A.
orchestralArrangement
chosen
Indicates that one musical work is arranged or adapted specifically for performance by an orchestra.
-
B.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
C.
hasOrchestralFeature
Indicates that something includes, exhibits, or is characterized by a notable orchestral element or component.
-
D.
hasBrassArrangement
Indicates that something includes or is associated with a musical arrangement specifically written for brass instruments.
-
E.
hasOrchestralSuite
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e054048ff48190ad107c890ef73166 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.