Triple
T24424241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agaléga |
E615811
|
entity |
| Predicate | usesHealthSystemSupportFrom |
P43935
|
FINISHED |
| Object | Mauritius |
—
|
NE NERFINISHED |
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: Mauritius | Statement: [Agaléga, usesHealthSystemSupportFrom, Mauritius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHealthSystemSupportFrom Context triple: [Agaléga, usesHealthSystemSupportFrom, Mauritius]
-
A.
hasOwnHealthSystem
Indicates that an entity operates and controls its own dedicated healthcare system, rather than relying solely on external or shared health services.
-
B.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
-
C.
hasHealthServicesCoordination
chosen
Indicates that one entity is responsible for organizing, managing, or facilitating access to health-related services for another entity.
-
D.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
E.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a4e3e4819094ac0941da5ca641 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.