Triple
T33114028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somewhere Gone |
E847408
|
entity |
| Predicate | followsGenreRootsOf |
P20936
|
FINISHED |
| Object | punk |
—
|
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: punk | Statement: [Somewhere Gone, followsGenreRootsOf, punk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsGenreRootsOf Context triple: [Somewhere Gone, followsGenreRootsOf, punk]
-
A.
hasGenreRelation
Indicates that there is an association between an entity and a specific genre, specifying the type or category it belongs to.
-
B.
associatedWithGenreCycle
Indicates a relationship where something (such as a work, event, or entity) is linked to or belongs to a recurring pattern or series defined by a particular genre.
-
C.
influencedByGenre
chosen
Indicates that something’s characteristics, style, or development are shaped or affected by a particular genre.
-
D.
isAssociatedWithSubgenre
Indicates that one entity has a connection or linkage to a specific subgenre of a broader category.
-
E.
referencedInGenre
Indicates that one entity is mentioned, cited, or otherwise referred to within the context of a particular 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 1, 2026, 1:27 a.m.