Triple

T34004623
Position Surface form Disambiguated ID Type / Status
Subject Pijpelijntjes E871923 entity
Predicate hasProtagonistSexualOrientation P88125 FINISHED
Object homosexual 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: homosexual | Statement: [Pijpelijntjes, hasProtagonistSexualOrientation, homosexual]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasProtagonistSexualOrientation
Context triple: [Pijpelijntjes, hasProtagonistSexualOrientation, homosexual]
  • A. sexualOrientation
    Indicates an entity’s enduring pattern of romantic or sexual attraction toward others, typically in terms of the genders or sexes to which it is attracted.
  • B. leadActorSexualOrientation
    Indicates the sexual orientation of the lead actor in a work or production.
  • C. sexualOrientationRevealedIn
    Indicates that an entity’s sexual orientation is disclosed, made known, or becomes apparent within a specified context, medium, or situation.
  • D. hasLGBTCharacter chosen
    Indicates that the subject includes, features, or is associated with one or more characters who identify as lesbian, gay, bisexual, or transgender.
  • E. hasSexualityCharacteristic
    Indicates that an entity possesses a specific sexual orientation or sexuality-related characteristic.
  • 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_69f349a08848819084b348d64c1879c3 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_6a021f84715881908e25b6548e7cf62e completed May 11, 2026, 6:27 p.m.
PD Predicate disambiguation batch_6a021739b7288190a4ca94c04074c78a completed May 11, 2026, 5:51 p.m.
Created at: May 1, 2026, 1:50 a.m.