Triple
T28423664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-63 |
E720011
|
entity |
| Predicate | spaceStationRendezvous |
P35735
|
FINISHED |
| Object | Mir |
—
|
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: Mir | Statement: [STS-63, spaceStationRendezvous, Mir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceStationRendezvous Context triple: [STS-63, spaceStationRendezvous, Mir]
-
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.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
C.
spacecraftDestination
chosen
Indicates that a spacecraft is intended to travel to, arrive at, or be directed toward a particular destination.
-
D.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 1:35 a.m.