Triple
T15474844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | surface-wave magnitude scale |
E376756
|
entity |
| Predicate | hasQuantityKind |
P73891
|
FINISHED |
| Object | logarithmic magnitude |
—
|
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: logarithmic magnitude | Statement: [surface-wave magnitude scale, hasQuantityKind, logarithmic magnitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuantityKind Context triple: [surface-wave magnitude scale, hasQuantityKind, logarithmic magnitude]
-
A.
belongsToQuantityKind
chosen
Indicates that something is associated with, or classified under, a particular kind or category of quantity (such as length, mass, or time).
-
B.
hasBaseQuantity
Indicates that something is associated with or defined in terms of a fundamental underlying quantity.
-
C.
usesQuantity
Indicates that one entity employs or applies a specified amount or measure of another entity in performing an action or fulfilling a function.
-
D.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
-
E.
quantificationType
Indicates the specific kind or category of quantity or measurement being applied in a given 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6e859481909c3d08343b7ad27c |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.