Triple
T7744879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Virginia Seismic Zone |
E175601
|
entity |
| Predicate | hasHistoricalSeismicity |
P12618
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Central Virginia Seismic Zone, hasHistoricalSeismicity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSeismicity Context triple: [Central Virginia Seismic Zone, hasHistoricalSeismicity, yes]
-
A.
hasEarthquakes
chosen
Indicates that the specified location or region experiences one or more earthquakes.
-
B.
hasGeologicalActivity
Indicates that an entity exhibits or is associated with ongoing or past geological processes such as volcanism, tectonics, or seismic activity.
-
C.
earthquakeHazardLevel
Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
-
D.
seismicSignificance
Indicates the degree to which something is relevant, influential, or important in the context of seismic activity or earthquake-related phenomena.
-
E.
earthquakeSequence
Indicates a relationship where multiple earthquakes are linked as part of the same temporal or causal sequence of seismic events.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.