Triple

T34288566
Position Surface form Disambiguated ID Type / Status
Subject Houris E879812 entity
Predicate genderInterpretation P29781 FINISHED
Object sometimes interpreted as gender-neutral 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: sometimes interpreted as gender-neutral | Statement: [Houris, genderInterpretation, sometimes interpreted as gender-neutral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: genderInterpretation
Context triple: [Houris, genderInterpretation, sometimes interpreted as gender-neutral]
  • A. genderConfiguration
    Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
  • B. genderImplication
    Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
  • C. genderDivision
    Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
  • D. genderRule chosen
    Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
  • E. genderCustom
    Indicates that an entity has a user-specified or non-standard gender designation beyond predefined gender categories.
  • 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_69f349b6df1c81908e5e5b6c2ab6409b completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7234bcaa48190ac970759d34e254a completed May 3, 2026, 10:28 a.m.
PD Predicate disambiguation batch_69f72155c48881909bd40b9aa3febd5a completed May 3, 2026, 10:20 a.m.
Created at: May 1, 2026, 1:57 a.m.