Triple
T5070354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spike |
E114261
|
entity |
| Predicate | hasSubcultureContext |
P1439
|
FINISHED |
| Object | post-punk 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: post-punk scene | Statement: [Spike, hasSubcultureContext, post-punk scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureContext Context triple: [Spike, hasSubcultureContext, post-punk scene]
-
A.
hasSubcultureDebate
Indicates that there is an ongoing or notable debate, disagreement, or contested discourse within or about a particular subculture.
-
B.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
C.
hasCulturalConcept
Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
-
D.
hasHeritageContext
Indicates that something is associated with, influenced by, or situated within a particular cultural, historical, or heritage-related context.
-
E.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74a0aa048190ba01281f1b160609 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.