Triple
T36096481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Progress M-34 |
E1044075
|
entity |
| Predicate | spaceStationInvolvedInCollision |
P70310
|
FINISHED |
| Object | Mir |
—
|
NE NERFINISHED |
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: Mir | Statement: [Progress M-34, spaceStationInvolvedInCollision, Mir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceStationInvolvedInCollision Context triple: [Progress M-34, spaceStationInvolvedInCollision, Mir]
-
A.
associatedWithSpacecraftImpact
chosen
Indicates that an entity is related to, involved in, or results from the impact of a spacecraft.
-
B.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
C.
spacecraftReentry
Indicates the event or process of a spacecraft returning from space and re-entering a planetary atmosphere.
-
D.
spaceStationReentryDate
Indicates the date on which a space station reenters the Earth's atmosphere or is deorbited.
-
E.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:08 p.m.