Triple
T36118429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salyut 6 |
E1044672
|
entity |
| Predicate | enabledCrewRotation |
P142967
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Salyut 6, enabledCrewRotation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enabledCrewRotation Context triple: [Salyut 6, enabledCrewRotation, yes]
-
A.
usesCrewRotationWith
Indicates that one entity applies a crew rotation system or schedule in conjunction with another entity.
-
B.
spacecraftUsedForCrewRotation
chosen
Indicates that a spacecraft is used to transport crew members to and/or from a space facility as part of scheduled crew rotation activities.
-
C.
isPermanentlyCrewed
Indicates that an object, such as a facility or vehicle, consistently has a crew present on a continuous, ongoing basis without planned periods of being uncrewed.
-
D.
hasExtendedCrew
Indicates that an entity is associated with an additional or supplementary group of crew members beyond its primary crew.
-
E.
usesGameRotation
Indicates that one entity applies or follows a specific game rotation pattern, schedule, or sequence in relation to another entity or 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.