Triple
T20891114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embryonic Journey |
E514407
|
entity |
| Predicate | hasPrimaryComposerInstrument |
P54631
|
FINISHED |
| Object | guitar |
—
|
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: guitar | Statement: [Embryonic Journey, hasPrimaryComposerInstrument, guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryComposerInstrument Context triple: [Embryonic Journey, hasPrimaryComposerInstrument, guitar]
-
A.
hasPrimaryMusician
Indicates that an entity has a specific musician designated as its main or principal performer.
-
B.
featuresPrimaryInstrument
chosen
Indicates that an entity is associated with the main or most prominent instrument used or highlighted in another entity (such as a work, performance, or recording).
-
C.
hasInstrumentalPerformer
Indicates that an action, event, or work is performed or carried out by an entity serving as its instrumental performer.
-
D.
hasMusicalComposer
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
E.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05e307081908f1d044e877017ec |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.