Triple
T3644686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | moment magnitude scale |
E77268
|
entity |
| Predicate | isDefinedFrom |
P27208
|
FINISHED |
| Object | seismic moment M0 |
—
|
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: seismic moment M0 | Statement: [moment magnitude scale, isDefinedFrom, seismic moment M0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefinedFrom Context triple: [moment magnitude scale, isDefinedFrom, seismic moment M0]
-
A.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
B.
previouslyDefinedIn
Indicates that something has been defined or introduced earlier in time or in a prior context relative to the current reference point.
-
C.
definedVia
chosen
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
-
D.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by another entity.
-
E.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or 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_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.