Triple

T36732608
Position Surface form Disambiguated ID Type / Status
Subject Site B E907380 entity
Predicate usedForInFiction P50195 FINISHED
Object genetic engineering experiments 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: genetic engineering experiments | Statement: [Site B, usedForInFiction, genetic engineering experiments]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedForInFiction
Context triple: [Site B, usedForInFiction, genetic engineering experiments]
  • A. usedInFictionalWork
    Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
  • B. fictionalUse chosen
    Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
  • C. worksUnderInFiction
    Indicates that, within a fictional context or narrative, one character or entity is hierarchically subordinate to and takes direction from another.
  • D. createsInFiction
    Indicates that one entity is the creator or originator of another entity within a fictional or narrative context.
  • E. worksWithInFiction
    Indicates that two fictional characters are depicted as collaborating, interacting, or being associated with each other within a narrative work.
  • 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_69f76e75aa6881909b844d00a3888ee5 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd4f39b5008190b83b3227ce22c509 completed May 8, 2026, 2:49 a.m.
PD Predicate disambiguation batch_69fd4df17c548190a4e2a6fea70f7e10 completed May 8, 2026, 2:44 a.m.
Created at: May 3, 2026, 4:12 p.m.