Triple
T326189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McGill University Health Centre |
E6523
|
entity |
| Predicate | hasMainFunction |
P88
|
FINISHED |
| Object | specialized clinical care |
—
|
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: specialized clinical care | Statement: [McGill University Health Centre, hasMainFunction, specialized clinical care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainFunction Context triple: [McGill University Health Centre, hasMainFunction, specialized clinical care]
-
A.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
C.
hasMainTrunkLine
Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
-
D.
hasMainSpeaker
Indicates that one entity serves as the primary or principal speaker associated with another entity, such as an event, recording, or presentation.
-
E.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e949364c8190bc2351f5413f5057 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.