Triple

T38407365
Position Surface form Disambiguated ID Type / Status
Subject Claymoore Psychiatric Hospital E901368 entity
Predicate hasFictionalWardType P202487 FINISHED
Object locked ward 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: locked ward | Statement: [Claymoore Psychiatric Hospital, hasFictionalWardType, locked ward]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalWardType
Context triple: [Claymoore Psychiatric Hospital, hasFictionalWardType, locked ward]
  • A. hasFictionalAdministration
    Indicates that an entity is governed, managed, or overseen by an administration that is fictional rather than real.
  • B. hasFictionalType
    Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
  • C. hasFictionalEstablishmentType
    Indicates that an establishment is associated with a particular type or category of fictional setting or institution.
  • D. hasFictionalStudentBodyType
    Indicates that an entity is characterized by a type or category of student body that exists in a fictional or imaginary context.
  • E. hasFictionalClinic
    Indicates that an entity is associated with or contains a clinic that exists only in a fictional or imaginary context.
  • 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_69f76e61e79c81908b787d83b46ab92b completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_6a0087de41c48190b2743a26b6d65409 completed May 10, 2026, 1:27 p.m.
PD Predicate disambiguation batch_6a00870a8bc48190be1385579b8cc1dd completed May 10, 2026, 1:24 p.m.
PDg Predicate description generation batch_6a0087dd79788190911609d406255be3 completed May 10, 2026, 1:27 p.m.
Created at: May 3, 2026, 4:31 p.m.