Triple
T21688693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar Bomba test site |
E535299
|
entity |
| Predicate | testAltitudeCategory |
P144928
|
FINISHED |
| Object | high-altitude airburst |
—
|
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: high-altitude airburst | Statement: [Tsar Bomba test site, testAltitudeCategory, high-altitude airburst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testAltitudeCategory Context triple: [Tsar Bomba test site, testAltitudeCategory, high-altitude airburst]
-
A.
approximateElevationCategory
Indicates the general elevation range or level into which an entity’s height above sea level has been coarsely grouped.
-
B.
extendsToApproximateAltitude
Indicates that something reaches or stretches up to a specified altitude value, which is understood to be approximate rather than exact.
-
C.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
operationalAltitude
Indicates the typical or designated altitude at which an entity is intended to operate.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:44 p.m.