Triple
T20872690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miles in the Sky |
E513933
|
entity |
| Predicate | featuresElectricInstruments |
P12878
|
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: [Miles in the Sky, featuresElectricInstruments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresElectricInstruments Context triple: [Miles in the Sky, featuresElectricInstruments, true]
-
A.
usesElectricGuitar
Indicates that an entity performs, creates, or is associated with an action or role that involves playing or employing an electric guitar.
-
B.
hasElectricGuitar
Indicates that an entity possesses or is associated with an electric guitar.
-
C.
instruments
Indicates that an agent uses a tool, device, or means to carry out an action or achieve an effect.
-
D.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
E.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c465693881909fe4c756ddc4f291 |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.