Triple
T8449389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Made in Britain |
E199762
|
entity |
| Predicate | featuresSubculture |
P3114
|
FINISHED |
| Object | skinhead |
—
|
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: skinhead | Statement: [Made in Britain, featuresSubculture, skinhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSubculture Context triple: [Made in Britain, featuresSubculture, skinhead]
-
A.
notableSubculture
Indicates that one entity is a significant or well-recognized subculture within the context or domain of the other entity.
-
B.
cultureCharacteristic
Indicates that a particular trait, practice, or feature is a defining characteristic of a given culture.
-
C.
popularCultureTrait
Indicates that an entity exhibits a characteristic, behavior, or element that is commonly recognized or influential within popular culture.
-
D.
hasCulturalFeature
chosen
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
E.
culturalThemes
Indicates that there is a relationship between entities where one embodies, expresses, or is associated with particular cultural themes present in or derived from the other.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44707b88190b3d8b30c45ef4496 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:09 p.m.