Triple
T876808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1755 Lisbon earthquake |
E18935
|
entity |
| Predicate | magnitudeEstimate |
P2981
|
FINISHED |
| Object | 8.5–9.0 Mw |
—
|
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: 8.5–9.0 Mw | Statement: [1755 Lisbon earthquake, magnitudeEstimate, 8.5–9.0 Mw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: magnitudeEstimate Context triple: [1755 Lisbon earthquake, magnitudeEstimate, 8.5–9.0 Mw]
-
A.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
-
B.
magnitude
Indicates a relationship where a quantitative size, extent, or intensity is assigned to or compared between entities or values.
-
C.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
D.
approximateMass
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
E.
maximumReach
Indicates the greatest extent, distance, or limit that something can reach or influence within 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acaf30a48190a10ed7fee464c444 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.