Triple
T27752876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 6 |
E701255
|
entity |
| Predicate | spacecraftDocked |
P142959
|
FINISHED |
| Object | Soyuz TMA-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: Soyuz TMA-1 | Statement: [Expedition 6, spacecraftDocked, Soyuz TMA-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftDocked Context triple: [Expedition 6, spacecraftDocked, Soyuz TMA-1]
-
A.
dockingWithISS
chosen
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.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
-
C.
firstCrewedDocking
Indicates the event in which a spacecraft docks with another vehicle or station with a crew on board for the first time.
-
D.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
-
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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 4:21 p.m.