Triple

T35928395
Position Surface form Disambiguated ID Type / Status
Subject Chemici E1039087 entity
Predicate hasFanCultureType P62120 FINISHED
Object local industrial community identity 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: local industrial community identity | Statement: [Chemici, hasFanCultureType, local industrial community identity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFanCultureType
Context triple: [Chemici, hasFanCultureType, local industrial community identity]
  • A. fanCultureElement
    Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
  • B. hasFanCommunity
    Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
  • C. hasFandomElement
    Indicates that something includes, features, or is associated with an element derived from or related to a fandom.
  • D. hasFandomAssociation
    Indicates a relationship where an entity is associated with, connected to, or recognized within a particular fandom or fan community.
  • E. fandomType chosen
    Indicates the specific category or kind of fandom relationship that exists between an entity and the subject of that fandom.
  • 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_69f76e23e4688190a5369138755138bf completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fe38be079c8190a240191ac0e73e3a completed May 8, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69fe350344508190930de2218156ca02 completed May 8, 2026, 7:09 p.m.
Created at: May 3, 2026, 4:07 p.m.