Triple
T1656865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-107 |
E35817
|
entity |
| Predicate | foamStrikeEvent |
P30967
|
FINISHED |
| Object | insulating foam shed from external tank struck left wing |
—
|
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: insulating foam shed from external tank struck left wing | Statement: [STS-107, foamStrikeEvent, insulating foam shed from external tank struck left wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foamStrikeEvent Context triple: [STS-107, foamStrikeEvent, insulating foam shed from external tank struck left wing]
-
A.
fellOn
Indicates that one entity moved downward, typically due to gravity, and came to rest on the surface of another entity.
-
B.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
C.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of another entity.
-
D.
fledDuring
Indicates that one entity escaped or ran away during the time period or event represented by the other entity.
-
E.
hasNearbyFell
Indicates that one entity has a fell (a hill or high moorland area) located in close proximity to it.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a99a4c3810819089d2dd0e23c8e46b |
completed | March 5, 2026, 2:59 p.m. |
Created at: March 4, 2026, 7:29 p.m.