Triple
T13529119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spektr |
E323085
|
entity |
| Predicate | resultOfCollision |
P93120
|
FINISHED |
| Object | depressurization of module |
—
|
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: depressurization of module | Statement: [Spektr, resultOfCollision, depressurization of module]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfCollision Context triple: [Spektr, resultOfCollision, depressurization of module]
-
A.
consequenceOfCollision
Indicates that one event, state, or condition occurs as a direct result of a collision between entities.
-
B.
collisionResult
chosen
Indicates the outcome or consequence that occurs when two or more entities collide.
-
C.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
D.
crashResultedIn
Indicates that a crash event caused or led to a particular outcome, consequence, or result.
-
E.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafba2c308190873efd15dfe26358 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:44 p.m.