Triple
T8955173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gazans |
E213453
|
entity |
| Predicate | healthcareAccess |
P85856
|
FINISHED |
| Object | limited and frequently disrupted |
—
|
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: limited and frequently disrupted | Statement: [Gazans, healthcareAccess, limited and frequently disrupted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healthcareAccess Context triple: [Gazans, healthcareAccess, limited and frequently disrupted]
-
A.
healthcareType
Indicates the category or kind of healthcare service, system, or coverage associated with an entity.
-
B.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
-
C.
hasHealthcareInfrastructure
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
D.
healthSystemLevel
Indicates the level or tier within a health system at which a given action, service, or relationship occurs (e.g., local, regional, national).
-
E.
positionOnHealthCare
Indicates a person or entity’s stance, opinion, or policy preference regarding health care systems, services, or reforms.
- F. None of above. chosen
Provenance (4 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6726cec48190a900ae52b1522adb |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.