Triple
T31413252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hospital Insurance |
E801323
|
entity |
| Predicate | appliesSetting |
P89047
|
FINISHED |
| Object | acute care 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: acute care hospitals | Statement: [Hospital Insurance, appliesSetting, acute care hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesSetting Context triple: [Hospital Insurance, appliesSetting, acute care hospitals]
-
A.
coversSetting
chosen
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
B.
revisedSetting
Indicates that an existing setting or configuration has been modified or updated from its previous state.
-
C.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state to another.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: April 30, 2026, 8:40 p.m.