Triple

T15447592
Position Surface form Disambiguated ID Type / Status
Subject Brian Percival E370063 entity
Predicate hasCreativeSpecialty P9512 FINISHED
Object historical drama direction 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: historical drama direction | Statement: [Brian Percival, hasCreativeSpecialty, historical drama direction]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCreativeSpecialty
Context triple: [Brian Percival, hasCreativeSpecialty, historical drama direction]
  • A. hasSpecialty
    Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
  • B. hasArtisticDiscipline chosen
    Indicates that one entity practices, specializes in, or is associated with a particular artistic discipline or field.
  • C. hasCreativeScope
    Indicates that one entity possesses authority or responsibility to make creative decisions or contributions within a defined domain or project.
  • D. craftSpecialty
    Indicates that an entity has a particular area of specialized skill or focus within a craft or artisanal practice.
  • E. hasSpecialist
    Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
  • 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ef767b4819099f2c0919a158321 completed April 16, 2026, 1:44 a.m.
PD Predicate disambiguation batch_69ded28276f481908c2038bb301e57cf completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:21 a.m.