Triple
T9355838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coal |
E225134
|
entity |
| Predicate | associatedHealthImpact |
P83771
|
FINISHED |
| Object | Respiratory diseases |
—
|
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: Respiratory diseases | Statement: [Coal, associatedHealthImpact, Respiratory diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHealthImpact Context triple: [Coal, associatedHealthImpact, Respiratory diseases]
-
A.
healthEffect
Indicates the impact or consequence that one entity has on the health or well-being of another.
-
B.
pollutionHealthEffect
chosen
Indicates the impact that a given source or level of pollution has on the health or well-being of affected entities.
-
C.
associatedConflictImpact
Indicates a relationship where an entity is linked to a specific conflict and the effects or consequences that conflict has on it.
-
D.
publicHealthSignificance
Indicates that something has importance, impact, or relevance for the health of the public or population at large.
-
E.
effectOnHealthCare
Indicates the impact or influence that something has on the quality, accessibility, cost, or delivery of health care services.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f99205c8190a5ad95926ef25497 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.