Triple

T29012937
Position Surface form Disambiguated ID Type / Status
Subject Slans E737216 entity
Predicate inUniverseOpposition P35001 FINISHED
Object humans ("normals") 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: humans ("normals") | Statement: [Slans, inUniverseOpposition, humans ("normals")]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseOpposition
Context triple: [Slans, inUniverseOpposition, humans ("normals")]
  • A. typeOfOpposition chosen
    Indicates a relationship where one entity stands in opposition or contrast to another, such as being a rival, adversary, or countering force.
  • B. inUniverse
    Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
  • C. opposesWorldSystem
    Indicates a relationship in which an entity actively resists, challenges, or works against the prevailing global order, structures, or dominant system of the world.
  • D. inUniverseAttitude
    Indicates the stance, feelings, or perspective that an entity holds toward something within the context of a specific fictional or defined universe.
  • E. activityWhenInOpposition
    Indicates that an activity occurs or is performed specifically during a time or condition of opposition between the involved entities.
  • 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_69f077ee19f881909af48f9cab00a2e5 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 28, 2026, 9:43 a.m.