Triple
T7744759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineral, Virginia |
E175598
|
entity |
| Predicate | eventEpicenterOf |
P1939
|
FINISHED |
| Object | 2011 Virginia earthquake |
—
|
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: 2011 Virginia earthquake | Statement: [Mineral, Virginia, eventEpicenterOf, 2011 Virginia earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventEpicenterOf Context triple: [Mineral, Virginia, eventEpicenterOf, 2011 Virginia earthquake]
-
A.
epicenter
chosen
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
-
B.
eventLocationOfNotableActivity
Indicates that a location is the place where a notable or significant activity or event involving the related entity occurred.
-
C.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
eventDescription
Indicates that a textual summary or explanation is provided describing what happens in the event.
- 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.