Triple
T36118389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Progress 7K-TG |
E1044671
|
entity |
| Predicate | spaceStationTypeServiced |
P52854
|
FINISHED |
| Object | Salyut |
—
|
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 | Statement: [Progress 7K-TG, spaceStationTypeServiced, Salyut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceStationTypeServiced Context triple: [Progress 7K-TG, spaceStationTypeServiced, Salyut]
-
A.
spaceStationType
Indicates the specific functional or structural category to which a space station belongs (e.g., research, military, commercial).
-
B.
spaceStationServed
chosen
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
-
C.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
D.
spacecraftServedOn
Indicates that a particular spacecraft is one on which an entity (typically a person) has served or been assigned.
-
E.
spaceStationAssociation
Indicates an affiliation or operational relationship between an entity and a specific space station, such as ownership, management, use, or service connection.
- 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_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:08 p.m.