Triple
T23368832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbie |
E593402
|
entity |
| Predicate | hasSubcultureInfluence |
P136681
|
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: [Abbie, hasSubcultureInfluence, punk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubcultureInfluence Context triple: [Abbie, hasSubcultureInfluence, punk]
-
A.
influencedSubculture
chosen
Indicates that one entity has had a shaping or significant impact on the development, style, or practices of a particular subculture.
-
B.
hasEthnicInfluence
Indicates that one entity has a cultural, traditional, or ethnic impact on, or contributes to shaping the ethnic character of, another entity.
-
C.
basedOnSubculture
Indicates that something is derived from, influenced by, or rooted in a particular subculture.
-
D.
hasCulturalImpact
Indicates that one entity has influenced, shaped, or significantly affected the culture, values, practices, or artistic expressions of another.
-
E.
hasCulturalRoots
Indicates that something originates from, is shaped by, or is deeply connected to particular cultural traditions, practices, or heritage.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aed374819097d38f51894bee44 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.