Triple
T16367270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinth Rift |
E397467
|
entity |
| Predicate | isKeySiteFor |
P7849
|
FINISHED |
| Object | studies of earthquake mechanics |
—
|
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: studies of earthquake mechanics | Statement: [Corinth Rift, isKeySiteFor, studies of earthquake mechanics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeySiteFor Context triple: [Corinth Rift, isKeySiteFor, studies of earthquake mechanics]
-
A.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
isKeyRegionFor
Indicates that one region plays a central or strategically important role in relation to a specified process, function, or larger area.
-
C.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
D.
isKeyConnectionPointFor
Indicates that something serves as a primary or critical linking point that connects or integrates other elements within a system or structure.
-
E.
isKeyPostIn
Indicates that a post or position is a central, strategically important element within a specified organization, structure, or context.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3de3d88190a42cd708746c8bd0 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.