Triple
T36482741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz program (space station operations phase) |
E898860
|
entity |
| Predicate | startUseWithStation |
P202686
|
FINISHED |
| Object | Salyut 1 |
—
|
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 1 | Statement: [Soyuz program (space station operations phase), startUseWithStation, Salyut 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUseWithStation Context triple: [Soyuz program (space station operations phase), startUseWithStation, Salyut 1]
-
A.
startingStation
Indicates the station or location where a journey, route, or trip begins.
-
B.
connectsAtStation
Indicates that one transportation service or route links to another at a specific station, allowing passengers to transfer between them there.
-
C.
stationOnLine
Indicates that a particular station is located on or served by a specific transit line.
-
D.
ownedStation
Indicates that one entity possesses ownership or control over a particular station.
-
E.
formerStationOnLine
Indicates that a station previously belonged to or operated on a particular transit line but is no longer in service on that line.
- F. None of above. chosen
Provenance (4 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_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_6a00acf7923c819091ae7fbda05164f6 |
completed | May 10, 2026, 4:06 p.m. |
Created at: May 3, 2026, 4:10 p.m.