Triple
T34402974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soyuz 21 |
E883030
|
entity |
| Predicate | spaceStationVisitedInstanceOf |
P21539
|
FINISHED |
| Object | Almaz military space station |
—
|
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: Almaz military space station | Statement: [Soyuz 21, spaceStationVisitedInstanceOf, Almaz military space station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceStationVisitedInstanceOf Context triple: [Soyuz 21, spaceStationVisitedInstanceOf, Almaz military space station]
-
A.
cargoSpacecraftVisited
Indicates that a cargo spacecraft has made a visit to a particular location or object.
-
B.
spaceStationServed
Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
-
C.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
D.
spacecraftVisited
Indicates that a spacecraft has traveled to and reached a particular location or celestial body.
-
E.
spaceStationVisit
chosen
Indicates that an entity travels to and spends time at a space station as a visitor or temporary occupant.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1:59 a.m.