Triple
T13528961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir core module |
E323082
|
entity |
| Predicate | providesLifeSupportFor |
P64179
|
FINISHED |
| Object | Mir space station crew |
—
|
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: Mir space station crew | Statement: [Mir core module, providesLifeSupportFor, Mir space station crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesLifeSupportFor Context triple: [Mir core module, providesLifeSupportFor, Mir space station crew]
-
A.
crewLifeSupportCapability
chosen
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
B.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
C.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another entity.
-
D.
supportsMedEvacOperations
Indicates the capability or role of providing assistance, resources, or infrastructure necessary to conduct medical evacuation operations.
-
E.
usedMeansToRescue
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
- 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.