Triple
T11022104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuujjuaq |
E260514
|
entity |
| Predicate | healthServices |
P7500
|
FINISHED |
| Object | regional health centre |
—
|
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: regional health centre | Statement: [Kuujjuaq, healthServices, regional health centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthServices Context triple: [Kuujjuaq, healthServices, regional health centre]
-
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.
healthcareAccess
Indicates the degree to which individuals can obtain and use needed health care services.
-
D.
healthSystemLevel
Indicates the level or tier within a health system at which a given action, service, or relationship occurs (e.g., local, regional, national).
-
E.
healthAuthority
Indicates that an entity serves as an official body responsible for overseeing, regulating, or managing health-related matters for another entity or within a specific jurisdiction.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797bd88188190a644adc9283cabb8 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.