Triple
T7744782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mineral, Virginia |
E175598
|
entity |
| Predicate | earthquakeDate2011 |
P12072
|
FINISHED |
| Object | 23 August 2011 |
—
|
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: 23 August 2011 | Statement: [Mineral, Virginia, earthquakeDate2011, 23 August 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earthquakeDate2011 Context triple: [Mineral, Virginia, earthquakeDate2011, 23 August 2011]
-
A.
earthquakeDate
chosen
Indicates the specific calendar date on which an earthquake event occurred.
-
B.
earthquakeDateRespondedTo
Indicates the date on which a response or action was taken in relation to a specific earthquake event.
-
C.
lastMajorEarthquakeYear
Indicates the calendar year in which the most recent major earthquake affecting the referenced entity occurred.
-
D.
earthquakeLocalTime
Indicates the local time at which an earthquake event occurred at its specific location.
-
E.
populationImpact2010Earthquake
Indicates the effect or consequences that the 2010 earthquake had on a population, such as changes in size, distribution, or demographic characteristics.
- 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.