Triple
T16939544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedan test |
E410914
|
entity |
| Predicate | depthOfBurst |
P36938
|
FINISHED |
| Object | 194 meters |
—
|
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: 194 meters | Statement: [Sedan test, depthOfBurst, 194 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthOfBurst Context triple: [Sedan test, depthOfBurst, 194 meters]
-
A.
detonationDepth
chosen
Indicates the depth or distance from a reference point at which a detonation occurs.
-
B.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
C.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
buriedDepth
Indicates the depth at which one entity is buried beneath a reference surface or another entity.
-
E.
designedTargetDepthInKilometers
Indicates the intended or planned depth, measured in kilometers, that something is designed to reach or operate at.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2c44288190a105761ae646989e |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.