Triple
T26443538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slob on My Knob |
E665149
|
entity |
| Predicate | hasSubcultureStatus |
P180596
|
FINISHED |
| Object | underground classic |
—
|
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: underground classic | Statement: [Slob on My Knob, hasSubcultureStatus, underground classic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureStatus Context triple: [Slob on My Knob, hasSubcultureStatus, underground classic]
-
A.
hasSubregionStatus
Indicates that one region holds an official or defined status as a subregion within a larger geographic or administrative area.
-
B.
hasSubcommunityIn
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
-
C.
basedOnSubculture
Indicates that something is derived from, influenced by, or rooted in a particular subculture.
-
D.
hasSubcultureDebate
Indicates that there is an ongoing or notable debate, disagreement, or contested discourse within or about a particular subculture.
-
E.
hasAssociatedCulture
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
- F. None of above. chosen
Provenance (4 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 27, 2026, midnight