Triple
T24955471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kadena Medical Clinic |
E624458
|
entity |
| Predicate | usesHealthSystem |
P15635
|
FINISHED |
| Object | TRICARE Pacific |
—
|
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: TRICARE Pacific | Statement: [Kadena Medical Clinic, usesHealthSystem, TRICARE Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHealthSystem Context triple: [Kadena Medical Clinic, usesHealthSystem, TRICARE Pacific]
-
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.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
C.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
-
D.
healthSystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
E.
hasHealthArea
Indicates that an entity is associated with, or falls within the scope of, a particular health-related domain or area of concern.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:57 a.m.