Triple
T21859168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1943 Tosya–Ladik earthquake |
E539714
|
entity |
| Predicate | epicentralRegion |
P38434
|
FINISHED |
| Object | between Tosya and Ladik |
—
|
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: between Tosya and Ladik | Statement: [1943 Tosya–Ladik earthquake, epicentralRegion, between Tosya and Ladik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epicentralRegion Context triple: [1943 Tosya–Ladik earthquake, epicentralRegion, between Tosya and Ladik]
-
A.
epicenter
Indicates the central point or focal location from which an event, influence, or effect originates or is most intensely experienced.
-
B.
epicenterState
Indicates the state in which the epicenter of an event (typically an earthquake) is located.
-
C.
distanceFromHypocenter
Indicates the measured distance between a specified location and the hypocenter (origin point) of an event such as an earthquake.
-
D.
relatedEarthquakeZone
chosen
Indicates that one entity is geographically or geologically associated with a particular earthquake-prone zone or seismic region.
-
E.
locationDuringEarthquake
Indicates the place where an entity is situated at the time an earthquake occurs.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63944d88190b6bd5e6ba4cc8ec1 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.