Triple

T15008185
Position Surface form Disambiguated ID Type / Status
Subject Anathema Device E377761 entity
Predicate inUniverseSkill P96902 FINISHED
Object prophecy interpretation 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: prophecy interpretation | Statement: [Anathema Device, inUniverseSkill, prophecy interpretation]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inUniverseSkill
Context triple: [Anathema Device, inUniverseSkill, prophecy interpretation]
  • A. inUniverseSpecialization
    Indicates that an entity’s specialization or area of focus exists specifically within the context or canon of a particular fictional universe.
  • B. indicatesSkill chosen
    Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
  • C. skilledIn
    Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
  • D. requiresSkill
    Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
  • E. hasEponymousSkill
    Indicates that an entity possesses a skill that is named after a particular person or entity.
  • 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_69d85cd3a3c881908c71fc424d459c17 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded73348d4819091d9e7f1b0fed822 completed April 15, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69de9a6531a88190acde65199a477350 completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:55 a.m.