Triple
T5622342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackenzie Vaughan Hospital |
E147636
|
entity |
| Predicate | hasDigitalInfrastructure |
P8220
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mackenzie Vaughan Hospital, hasDigitalInfrastructure, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalInfrastructure Context triple: [Mackenzie Vaughan Hospital, hasDigitalInfrastructure, yes]
-
A.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
B.
hasDigitalAccess
chosen
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
C.
hasDigitalInitiative
Indicates that an entity is engaged in or associated with a specific digital project, program, or transformation effort.
-
D.
hasGlobalInfrastructure
Indicates that an entity possesses infrastructure, facilities, or operational capabilities that are distributed across multiple countries or regions worldwide.
-
E.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022133eec819086acb04864dde5ee |
completed | March 22, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.