Triple

T20428298
Position Surface form Disambiguated ID Type / Status
Subject Apparition Test Centre E501061 entity
Predicate regulatesSkill P60803 FINISHED
Object Apparition 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: Apparition | Statement: [Apparition Test Centre, regulatesSkill, Apparition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatesSkill
Context triple: [Apparition Test Centre, regulatesSkill, Apparition]
  • A. 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.
  • B. indicatesSkill
    Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
  • C. regulatesCompetenceIn chosen
    Indicates that one entity controls, influences, or modulates the ability or readiness of another entity to perform a specific function or process.
  • D. developsSkill
    Indicates that one entity causes or contributes to the growth, improvement, or acquisition of a particular skill in another entity.
  • E. validatesSkill
    Indicates that one entity confirms or verifies the authenticity, correctness, or adequacy of another entity’s skill or competency.
  • 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_69e0b4aa68fc8190b1a14c55575ef04a completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67baa91b881909dfd68ccca25063c completed April 20, 2026, 7:16 p.m.
PD Predicate disambiguation batch_69e5766df0008190a73c4f613c29678f completed April 20, 2026, 12:42 a.m.
Created at: April 16, 2026, 11:31 a.m.