Triple
T26692039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-waves |
E672911
|
entity |
| Predicate | amplitude |
P1937
|
FINISHED |
| Object | generally smaller than S-wave amplitude at same distance |
—
|
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: generally smaller than S-wave amplitude at same distance | Statement: [P-waves, amplitude, generally smaller than S-wave amplitude at same distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amplitude Context triple: [P-waves, amplitude, generally smaller than S-wave amplitude at same distance]
-
A.
amplitudeDefinition
Indicates the relationship by which the amplitude of a signal, wave, or oscillation is formally specified or defined.
-
B.
outburstAmplitude
Indicates the magnitude or intensity level of an outburst event relative to a baseline or typical state.
-
C.
magnitude
chosen
Indicates a relationship where a quantitative size, extent, or intensity is assigned to or compared between entities or values.
-
D.
typicalAmplitudeRangeV
Indicates the usual numerical range of amplitude values associated with a given variable or signal.
-
E.
lightcurveAmplitude
Indicates the measured range of brightness variation of an object over time in its light curve.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6174310d48190b1ef1e515fed7990 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:26 a.m.