Triple
T38407367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claymoore Psychiatric Hospital |
E901368
|
entity |
| Predicate | hasFictionalFacilityFeature |
P202496
|
FINISHED |
| Object | patient bedrooms |
—
|
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: patient bedrooms | Statement: [Claymoore Psychiatric Hospital, hasFictionalFacilityFeature, patient bedrooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalFacilityFeature Context triple: [Claymoore Psychiatric Hospital, hasFictionalFacilityFeature, patient bedrooms]
-
A.
hasFictionalWardType
Indicates that an entity is associated with a ward characterized as a fictional or imaginary type.
-
B.
hasFacilityFunction
Indicates that a facility performs, supports, or is designated for a particular function or operational role.
-
C.
hasNearbyFictionalFeature
Indicates that an entity is located close to a fictional or imaginary geographic or structural feature.
-
D.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
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_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
| PDg | Predicate description generation | batch_6a008ac2d0dc8190865ccedb2003d0ed |
completed | May 10, 2026, 1:40 p.m. |
Created at: May 3, 2026, 4:31 p.m.