Triple
T960559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Solomon Islands |
E20725
|
entity |
| Predicate | naturalHazards |
P12618
|
FINISHED |
| Object | earthquakes |
—
|
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: earthquakes | Statement: [Southeastern Solomon Islands, naturalHazards, earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalHazards Context triple: [Southeastern Solomon Islands, naturalHazards, earthquakes]
-
A.
hasEarthquakes
chosen
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
naturalResources
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
C.
tectonicEvents
Indicates the occurrence or involvement of entities in geological processes related to the movement and interaction of Earth’s tectonic plates, such as earthquakes, volcanic activity, or continental drift.
-
D.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
E.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4144c208190980936347a95e233 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a2e23c8190b932fe88b02f995d |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.