Triple
T1522396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mae Sot |
E32257
|
entity |
| Predicate | hasHealthcareFacilityType |
P2836
|
FINISHED |
| Object | mission hospitals |
—
|
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: mission hospitals | Statement: [Mae Sot, hasHealthcareFacilityType, mission hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthcareFacilityType Context triple: [Mae Sot, hasHealthcareFacilityType, mission hospitals]
-
A.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
B.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
C.
hasMedicalCenter
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
-
D.
isPublicHospital
Indicates that a hospital is owned, funded, or operated by a government or public authority rather than by private entities.
-
E.
hasAffiliatedHospital
Indicates that one entity (typically a medical professional, clinic, or organization) is formally connected or associated with a particular hospital for professional or operational purposes.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.