Triple

T37508928
Position Surface form Disambiguated ID Type / Status
Subject Skolex, the Insatiable Ravener E932166 entity
Predicate bossOrdering P37518 FINISHED
Object early boss in Sepulcher of the First Ones 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: early boss in Sepulcher of the First Ones | Statement: [Skolex, the Insatiable Ravener, bossOrdering, early boss in Sepulcher of the First Ones]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bossOrdering
Context triple: [Skolex, the Insatiable Ravener, bossOrdering, early boss in Sepulcher of the First Ones]
  • A. bossOrder
    Indicates that a boss issues a directive or command to a subordinate.
  • B. confersOrder
    Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
  • C. orderOf chosen
    Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
  • D. questOrderedBy
    Indicates that one entity is a quest that has been requested, assigned, or commissioned by another entity.
  • E. establishedInOrder
    Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
  • 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_69f76ec5268481909ea01c73aeeefd42 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba5eec0448190a5e6f0c43fdcd0e3 completed May 6, 2026, 8:34 p.m.
PD Predicate disambiguation batch_69fba34edd548190bfa980e6e16e0a88 completed May 6, 2026, 8:23 p.m.
Created at: May 3, 2026, 4:17 p.m.