Triple
T26692050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-waves |
E672911
|
entity |
| Predicate | comparedToSurfaceWaves |
P167299
|
FINISHED |
| Object | arrive earlier than surface waves |
—
|
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: arrive earlier than surface waves | Statement: [P-waves, comparedToSurfaceWaves, arrive earlier than surface waves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparedToSurfaceWaves Context triple: [P-waves, comparedToSurfaceWaves, arrive earlier than surface waves]
-
A.
seismicWavePropagation
Indicates the transmission and movement of seismic waves through different materials or regions over time.
-
B.
surfaceDisplacement
Indicates a change in the position or configuration of a surface relative to its original state.
-
C.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
D.
surfaceGravityAnomaly
Indicates a deviation of an object's local surface gravitational acceleration from a reference or expected gravitational field.
-
E.
surfaceRupture
Indicates that a geological fault movement has broken through to and displaced the Earth's surface.
- F. None of above. chosen
Provenance (4 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 27, 2026, 3:26 a.m.