Triple
T10220803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groningen earthquake zone |
E242571
|
entity |
| Predicate | timePeriodOfIntenseActivity |
P70162
|
FINISHED |
| Object | 1990s–2020s |
—
|
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: 1990s–2020s | Statement: [Groningen earthquake zone, timePeriodOfIntenseActivity, 1990s–2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfIntenseActivity Context triple: [Groningen earthquake zone, timePeriodOfIntenseActivity, 1990s–2020s]
-
A.
hasTimeOfHighActivity
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
B.
activityTime
Indicates the time period during which an activity occurs or is scheduled to take place.
-
C.
activityPeakPeriod
chosen
Indicates the time period during which an activity reaches its highest level or intensity.
-
D.
timePeriodOfMajorImportance
Indicates that a particular time period holds significant importance or prominence within a given context or domain.
-
E.
peakActivity
Indicates that an entity is at its highest or most intense level of activity within a given period or context.
- 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_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. |
Created at: April 6, 2026, 11:09 a.m.