Triple
T34847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Atlantic Ridge |
E692
|
entity |
| Predicate | earthquakeActivity |
P81
|
FINISHED |
| Object | frequent shallow earthquakes |
—
|
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: frequent shallow earthquakes | Statement: [Mid-Atlantic Ridge, earthquakeActivity, frequent shallow earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earthquakeActivity Context triple: [Mid-Atlantic Ridge, earthquakeActivity, frequent shallow earthquakes]
-
A.
locatedOnTectonicBoundary
Indicates that one entity is situated directly on or along the tectonic plate boundary associated with another entity.
-
B.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
C.
activity
chosen
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
D.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
E.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a24872e4e481908567850168d65015 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.