Triple
T10093766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asan |
E215809
|
entity |
| Predicate | hasHealthResource |
P72534
|
FINISHED |
| Object | therapeutic hot spring baths |
—
|
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: therapeutic hot spring baths | Statement: [Asan, hasHealthResource, therapeutic hot spring baths]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthResource Context triple: [Asan, hasHealthResource, therapeutic hot spring baths]
-
A.
hasHealthCode
Indicates that an entity is associated with a specific health-related classification or status code.
-
B.
hasHealthProgram
Indicates that an entity provides, administers, or is associated with a specific health-related program or initiative.
-
C.
hasHealthConcern
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
D.
hasHealthcareInfrastructure
chosen
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
E.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of 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_69ca83a4947c8190823a7495dc5d96ed |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05da3688190b7a1ac8a58e5488f |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.