Triple

T23886839
Position Surface form Disambiguated ID Type / Status
Subject Hairmyres E600356 entity
Predicate hasAmenity P105 FINISHED
Object Hairmyres Hospital
Hairmyres Hospital is a major acute care hospital in East Kilbride, Scotland, providing a range of emergency, inpatient, and outpatient medical services to the surrounding region.
E1606301 NE 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: Hairmyres Hospital | Statement: [Hairmyres, hasAmenity, Hairmyres Hospital]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hairmyres Hospital
Triple: [Hairmyres, hasAmenity, Hairmyres Hospital]
Generated description
Hairmyres Hospital is a major acute care hospital in East Kilbride, Scotland, providing a range of emergency, inpatient, and outpatient medical services to the surrounding region.

Provenance (5 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_69e295318e148190b9979d8fc02e168f completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1ccff46208190a8de3254dabd51ab completed April 29, 2026, 9:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f69cd9a5881908c76fe917918f87b completed May 21, 2026, 8:23 p.m.
NEDg Description generation batch_6a0f6dbf915c8190a820aa961f9007d0 completed May 21, 2026, 8:40 p.m.
NED2 Entity disambiguation (via description) batch_6a0f6e5bceb88190ae077c6b68bc25c1 completed May 21, 2026, 8:43 p.m.
Created at: April 17, 2026, 8:24 p.m.