Triple
T35411897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BMD-2 |
E1023533
|
entity |
| Predicate | parachuteSystemCompatibleWith |
P182927
|
FINISHED |
| Object | PRSM-915 |
—
|
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: PRSM-915 | Statement: [BMD-2, parachuteSystemCompatibleWith, PRSM-915]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parachuteSystemCompatibleWith Context triple: [BMD-2, parachuteSystemCompatibleWith, PRSM-915]
-
A.
parachuteSystemCompatible
chosen
Indicates that one system or component is suitable and safe for use with a specified parachute system, meeting required compatibility conditions.
-
B.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover another entity.
-
C.
parachuteType
Indicates the specific kind or category of parachute associated with an entity or event.
-
D.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
-
E.
parachuteMass
Indicates the mass or weight associated with a parachute in the described context.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:03 p.m.