Triple
T31921198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 27 |
E814972
|
entity |
| Predicate | spacecraftDockingPortUsed |
P14980
|
FINISHED |
| Object | Russian Orbital Segment |
—
|
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: Russian Orbital Segment | Statement: [Expedition 27, spacecraftDockingPortUsed, Russian Orbital Segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftDockingPortUsed Context triple: [Expedition 27, spacecraftDockingPortUsed, Russian Orbital Segment]
-
A.
dockingWithISS
Indicates a relationship where a spacecraft is physically connecting and securing itself to the International Space Station to enable transfer of crew, cargo, or resources.
-
B.
firstCrewedDocking
Indicates the event in which a spacecraft docks with another vehicle or station with a crew on board for the first time.
-
C.
spaceStationModuleUsed
Indicates that a particular space station module is utilized or occupied for a specific purpose or activity.
-
D.
dockingDateWithSalyut7
Indicates the date on which an entity docked with the Salyut 7 space station.
-
E.
dockingSystem
chosen
Indicates a relationship where one structure or vehicle is equipped with or connected to a system that enables secure docking with another compatible structure or vehicle.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.