Triple

T35208050
Position Surface form Disambiguated ID Type / Status
Subject The Man E1016592 entity
Predicate challengesTraditionalGenderRoles P89475 FINISHED
Object true 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: true | Statement: [The Man, challengesTraditionalGenderRoles, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: challengesTraditionalGenderRoles
Context triple: [The Man, challengesTraditionalGenderRoles, true]
  • A. genderNorms
    Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
  • B. roleInPatriarchalNarratives chosen
    Indicates how an entity functions within, reinforces, challenges, or is positioned by patriarchal storylines, structures, or discourses.
  • C. sexualRole
    Indicates the specific sexual function, position, or behavioral role one entity assumes in a sexual interaction or relationship with another.
  • D. hasGenderRole
    Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
  • E. stanceOnGenderIssues
    Indicates a person or entity’s views, attitudes, or position regarding gender-related topics, policies, or inequalities.
  • 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_69f76ddf549c8190869d0af076fd2c28 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f63c8788190b253a18de5ca1312 completed May 3, 2026, 6:09 p.m.
PD Predicate disambiguation batch_69f78e2d71248190b850c2802ec170c0 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:02 p.m.