Triple
T12949957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramstein airshow disaster |
E309865
|
entity |
| Predicate | groundImpactLocation |
P106351
|
FINISHED |
| Object | spectator area |
—
|
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: spectator area | Statement: [Ramstein airshow disaster, groundImpactLocation, spectator area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundImpactLocation Context triple: [Ramstein airshow disaster, groundImpactLocation, spectator area]
-
A.
terrainImpact
Indicates how the characteristics of the terrain influence or modify the outcome, behavior, or effectiveness of an action or interaction.
-
B.
fallLocation
chosen
Indicates the place or area where an entity falls or ends up after falling.
-
C.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
D.
locationGroundSegment
Indicates that one entity is located at or associated with a specific ground segment or ground-based infrastructure.
-
E.
groundingEvent
Indicates that an event serves as a foundational or reference occurrence upon which other events, interpretations, or relations are based.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.