Triple
T4636616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taal Lake |
E101546
|
entity |
| Predicate | hazardManagementConcern |
P57885
|
FINISHED |
| Object | evacuation of lakeshore communities during eruptions |
—
|
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: evacuation of lakeshore communities during eruptions | Statement: [Taal Lake, hazardManagementConcern, evacuation of lakeshore communities during eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardManagementConcern Context triple: [Taal Lake, hazardManagementConcern, evacuation of lakeshore communities during eruptions]
-
A.
hasManagementConcern
Indicates that one entity has responsibility, authority, or involvement in overseeing, directing, or managing another entity or activity.
-
B.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
hazardScope
Indicates the range or extent within which a particular hazard is relevant, applicable, or has effect.
-
D.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f7b94481909f3335312becd446 |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.