Triple
T3644656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | moment magnitude scale |
E77268
|
entity |
| Predicate | isLogarithmicWithBase |
P4234
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [moment magnitude scale, isLogarithmicWithBase, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLogarithmicWithBase Context triple: [moment magnitude scale, isLogarithmicWithBase, 10]
-
A.
logarithmBaseDetermines
chosen
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
-
B.
isGeometric
Indicates that something has the properties or form of a geometric figure, pattern, or structure.
-
C.
isProportionalTo
Indicates that one quantity varies in constant ratio to another, so when one changes, the other changes by a fixed multiplicative factor.
-
D.
allowsExponentType
Indicates that one entity permits or supports the use of a specified type for an exponent in an operation or expression.
-
E.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35c28908190b253f4835918a2b4 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.