Triple
T9314901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RQIA |
E224092
|
entity |
| Predicate | regulatedServiceType |
P34262
|
FINISHED |
| Object | nursing homes |
—
|
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: nursing homes | Statement: [RQIA, regulatedServiceType, nursing homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatedServiceType Context triple: [RQIA, regulatedServiceType, nursing homes]
-
A.
typeOfServiceRegulated
chosen
Indicates that a particular type of service is subject to regulation or oversight under a specified regulatory framework or authority.
-
B.
regulatesOrServes
Indicates that one entity controls, governs, or provides a service or function for another entity.
-
C.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
D.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
-
E.
plannedServiceType
Indicates the category or kind of service that has been scheduled or planned to be provided.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.