Triple
T38596288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Fly |
E934088
|
entity |
| Predicate | hasSubcultureFollowing |
P142344
|
FINISHED |
| Object | punk subculture |
—
|
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 subculture | Statement: [Human Fly, hasSubcultureFollowing, punk subculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureFollowing Context triple: [Human Fly, hasSubcultureFollowing, punk subculture]
-
A.
hasSubcultureStatus
Indicates that an entity holds a particular role, recognition, or standing within a specific subculture or subcultural context.
-
B.
hasCultFollowing
Indicates that something has attracted a small but highly dedicated and enthusiastic group of supporters or fans.
-
C.
hasSubcommunityIn
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
-
D.
followedCustom
Indicates that one entity chose to follow another entity according to a specific, non-standard or user-defined rule or configuration.
-
E.
basedOnSubculture
chosen
Indicates that something is derived from, influenced by, or rooted in a particular subculture.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: May 3, 2026, 4:32 p.m.