Triple
T37485915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorengau General Hospital |
E931529
|
entity |
| Predicate | hasApproximateLevelOfCare |
P139853
|
FINISHED |
| Object | secondary 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: secondary care | Statement: [Lorengau General Hospital, hasApproximateLevelOfCare, secondary care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateLevelOfCare Context triple: [Lorengau General Hospital, hasApproximateLevelOfCare, secondary care]
-
A.
hasFacilityLevel
Indicates the degree or tier of capability, service, or infrastructure that a particular facility possesses.
-
B.
hasEmergencyDepartmentLevel
Indicates the specific classification or tier of emergency care capability associated with an emergency department.
-
C.
hospitalLevel
chosen
Indicates the classification or rank of a hospital within a defined healthcare system or hierarchy.
-
D.
isAcuteCareFacility
Indicates that the entity functions as a healthcare facility providing short-term, intensive medical treatment for patients with severe or urgent conditions.
-
E.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.