Triple
T15461228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Atlantic region |
E371902
|
entity |
| Predicate | hasSeismicityLevel |
P34010
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Mid-Atlantic region, hasSeismicityLevel, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeismicityLevel Context triple: [Mid-Atlantic region, hasSeismicityLevel, moderate]
-
A.
earthquakeHazardLevel
chosen
Indicates the assessed degree of risk or potential impact from earthquakes associated with a given location or entity.
-
B.
hasSeismicBehavior
Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
-
C.
hasEarthquakes
Indicates that the specified location or region experiences one or more earthquakes.
-
D.
geologicHazardLevel
Indicates the degree of potential danger or risk posed by geologic processes or conditions at a given location.
-
E.
earthquakeDamageLevel
Indicates the severity or extent of damage caused by an earthquake to a given subject.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f17663c8190b995c7c3129c90d6 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:32 a.m.