Triple

T13105100
Position Surface form Disambiguated ID Type / Status
Subject San Angeles E310823 entity
Predicate hasCulturalAspectInFiction P106216 FINISHED
Object banned profanity 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: banned profanity | Statement: [San Angeles, hasCulturalAspectInFiction, banned profanity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCulturalAspectInFiction
Context triple: [San Angeles, hasCulturalAspectInFiction, banned profanity]
  • A. hasCulturalDepiction
    Indicates that one entity is represented, portrayed, or depicted in the cultural work or expression of another entity.
  • B. hasFeatureInFiction chosen
    Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
  • C. hasCulturalReference
    Indicates that one entity makes reference to, draws from, or is associated with the cultural content, symbols, or traditions represented by another entity.
  • D. hasPlaceInFiction
    Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
  • E. usedInCulture
    Indicates that something (such as an object, practice, or concept) is employed, referenced, or plays a role within a particular culture or cultural context.
  • 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98154c9f48190aeca779d97151759 completed April 10, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69d98041a3548190a05ddd83dbb660fa completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:05 p.m.