Triple
T14656798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Voyage |
E344130
|
entity |
| Predicate | decadeInfluence |
P108339
|
FINISHED |
| Object | 1970s jazz-funk scene |
—
|
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: 1970s jazz-funk scene | Statement: [Mystic Voyage, decadeInfluence, 1970s jazz-funk scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decadeInfluence Context triple: [Mystic Voyage, decadeInfluence, 1970s jazz-funk scene]
-
A.
influencedDecade
chosen
Indicates that one entity had a significant impact on shaping or affecting the events, trends, or characteristics of a specified decade.
-
B.
decadeRecognition
Indicates that an entity is formally recognized, honored, or notable during a specific decade.
-
C.
associatedDecadeInPopCulture
Indicates the decade in popular culture with which an entity is most closely linked or commonly recognized.
-
D.
decade
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
E.
decadeContext
Indicates that the relationship or fact is specifically situated within, or pertains to, a particular decade as its temporal context.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb51a562c819098971447db4b29f7 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:27 a.m.