Triple
T36482734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz program (space station operations phase) |
E898860
|
entity |
| Predicate | servesSpaceStation |
P52854
|
FINISHED |
| Object | Salyut space stations |
—
|
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: Salyut space stations | Statement: [Soyuz program (space station operations phase), servesSpaceStation, Salyut space stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesSpaceStation Context triple: [Soyuz program (space station operations phase), servesSpaceStation, Salyut space stations]
-
A.
spaceStationServed
chosen
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
-
B.
servedOnSpaceStation
Indicates that an entity performed duties or was stationed as part of the crew on a particular space station.
-
C.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
D.
mainSpaceStation
Indicates that one entity serves as the primary or central space station associated with another entity.
-
E.
servedOnSpaceShuttle
Indicates that an individual participated as a crew member on a mission aboard a Space Shuttle.
- 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_69f76e5a0e088190a2b6706aeb41723c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a00474f08908190bc8ae3b320ec887b |
completed | May 10, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_6a0045dc3bd48190a9e0520f3ef3f067 |
completed | May 10, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:10 p.m.