Triple
T21688736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Bomba |
E535300
|
entity |
| Predicate | seismicMagnitude |
P111021
|
FINISHED |
| Object | around 5.0–5.25 |
—
|
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: around 5.0–5.25 | Statement: [Tsar Bomba, seismicMagnitude, around 5.0–5.25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seismicMagnitude Context triple: [Tsar Bomba, seismicMagnitude, around 5.0–5.25]
-
A.
earthquakeMagnitude
Indicates the measured strength or intensity of an earthquake, typically expressed on a standardized magnitude scale.
-
B.
exampleMagnitude
Indicates a relationship where one entity serves as a representative or typical instance that illustrates the scale, size, or intensity (magnitude) of another entity or quantity.
-
C.
hasEstimatedMagnitude
chosen
Indicates that an entity is associated with an approximate or calculated value representing its magnitude or size.
-
D.
earthquakeMagnitudeRange
Indicates the range of magnitudes within which an earthquake’s measured strength falls.
-
E.
seismicMoment
Indicates the relationship between an earthquake event and the total energy it releases, quantified as its seismic moment.
- 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_69e0c469b6ec8190aee4cadd1527db91 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cd51d481908df67e4f69826b06 |
completed | April 27, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:44 p.m.