Triple
T37875575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuadrilla Resources |
E944709
|
entity |
| Predicate | 2011BlackpoolEarthquakesMagnitude |
P5297
|
FINISHED |
| Object | 2.3 |
—
|
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: 2.3 | Statement: [Cuadrilla Resources, 2011BlackpoolEarthquakesMagnitude, 2.3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 2011BlackpoolEarthquakesMagnitude Context triple: [Cuadrilla Resources, 2011BlackpoolEarthquakesMagnitude, 2.3]
-
A.
earthquakeDepth2011
Indicates the depth at which an earthquake event in the year 2011 occurred beneath the Earth's surface.
-
B.
earthquakeMagnitude
chosen
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
C.
populationImpact2010Earthquake
Indicates the effect or consequences that the 2010 earthquake had on a population, such as changes in size, distribution, or demographic characteristics.
-
D.
tornadoIntensity2011
Indicates the intensity level associated with a tornado event that occurred in 2011.
-
E.
notableAftershockMagnitude
Indicates that the magnitude value corresponds to a particularly significant or noteworthy aftershock following a main seismic 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.