Triple

T5402100
Position Surface form Disambiguated ID Type / Status
Subject Bond (Dead by Daylight perk) E120800 entity
Predicate revealsAurasOf P63764 FINISHED
Object nearby teammates 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: nearby teammates | Statement: [Bond (Dead by Daylight perk), revealsAurasOf, nearby teammates]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: revealsAurasOf
Context triple: [Bond (Dead by Daylight perk), revealsAurasOf, nearby teammates]
  • A. hasModeOfRevelation
    Indicates the manner or channel through which something is revealed, communicated, or made known.
  • B. hasRitualElements
    Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
  • C. hasRitualFocus
    Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
  • D. appearsInRitual
    Indicates that an entity is included, featured, or participates as a component or element within a specific ritual.
  • E. hasRitualSpace
    Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
  • F. None of above. chosen

Provenance (4 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_69bd46391c0c81909fa484446732b6a3 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd8932b8bc8190bd31e11b167a7212 completed March 20, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69bd84660ea08190a641084814fcf94d completed March 20, 2026, 5:31 p.m.
PDg Predicate description generation batch_69bd8931302c81908afcb0f011e91f09 completed March 20, 2026, 5:51 p.m.
Created at: March 20, 2026, 2:04 p.m.