Triple
T26894298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacobabad |
E677858
|
entity |
| Predicate | hasPublicHealthConcern |
P4720
|
FINISHED |
| Object | heat stress |
—
|
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: heat stress | Statement: [Jacobabad, hasPublicHealthConcern, heat stress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicHealthConcern Context triple: [Jacobabad, hasPublicHealthConcern, heat stress]
-
A.
hasHealthConcern
chosen
Indicates that an entity has a specific health-related issue, condition, or concern associated with it.
-
B.
publicHealthEmergencyOfInternationalConcern
Indicates that a health event is so serious, sudden, unusual, or unexpected that it poses a public health risk to other countries and may require a coordinated international response.
-
C.
hasManagementConcern
Indicates that one entity has responsibility, authority, or involvement in overseeing, directing, or managing another entity or activity.
-
D.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
E.
hasPandemicCause
Indicates that one entity is the underlying cause or origin of a pandemic affecting 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 5:47 a.m.