Triple
T10220807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groningen earthquake zone |
E242571
|
entity |
| Predicate | hasEarlyEarthquakesReportedSince |
P92817
|
FINISHED |
| Object | early 1990s |
—
|
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: early 1990s | Statement: [Groningen earthquake zone, hasEarlyEarthquakesReportedSince, early 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlyEarthquakesReportedSince Context triple: [Groningen earthquake zone, hasEarlyEarthquakesReportedSince, early 1990s]
-
A.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
earthquakeDateRespondedTo
Indicates the date on which a response or action was taken in relation to a specific earthquake event.
-
C.
earthquakeDate
Indicates the specific calendar date on which an earthquake event occurred.
-
D.
lastKnownGreatEarthquakeGenerated
Indicates that the referenced event is the most recent known great earthquake that produced or generated the associated effect or data.
-
E.
facedMajorEarthquake
Indicates that an entity has experienced or been subjected to a significant or severe earthquake event.
- 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_69d381ae26c48190985abd0e25ee5d04 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d3aa72b258819097d8d50a714e19dc |
completed | April 6, 2026, 12:43 p.m. |
| PD | Predicate disambiguation | batch_69d3955f61f88190b8d37ff645cd44d3 |
completed | April 6, 2026, 11:13 a.m. |
| PDg | Predicate description generation | batch_69d3aa208c248190a0fb186b106389f3 |
completed | April 6, 2026, 12:42 p.m. |
Created at: April 6, 2026, 11:09 a.m.