Triple
T5920109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grateful Dead Records |
E131678
|
entity |
| Predicate | parentGenreContext |
P20075
|
FINISHED |
| Object | American rock music industry |
—
|
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: American rock music industry | Statement: [Grateful Dead Records, parentGenreContext, American rock music industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentGenreContext Context triple: [Grateful Dead Records, parentGenreContext, American rock music industry]
-
A.
genreContext
chosen
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
-
B.
commonGenre
Indicates that two entities share at least one genre in common.
-
C.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
D.
gameGenreContext
Indicates the genre or type of game associated with a given game entity or gaming context.
-
E.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.