Triple
T6276261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosshouse Hospital |
E140666
|
entity |
| Predicate | healthcare |
P7500
|
FINISHED |
| Object | public |
—
|
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: public | Statement: [Crosshouse Hospital, healthcare, public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthcare Context triple: [Crosshouse Hospital, healthcare, public]
-
A.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
B.
healthcareType
chosen
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
C.
focusesOnMedicalCare
Indicates that one entity directs attention, resources, or activity specifically toward providing or improving medical care for another entity.
-
D.
positionOnHealthCare
Indicates a person or entity’s stance, opinion, or policy preference regarding health care systems, services, or reforms.
-
E.
healthSystemLevel
Indicates the level or tier within a health system at which a given action, service, or relationship occurs (e.g., local, regional, national).
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063d96fbc8190a9091456b82762d1 |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c05608a5608190b22a1fdc4060470d |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.