Triple
T31921181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 27 |
E814972
|
entity |
| Predicate | visitingShuttleMission |
P135906
|
FINISHED |
| Object | STS-134 |
—
|
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: STS-134 | Statement: [Expedition 27, visitingShuttleMission, STS-134]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitingShuttleMission Context triple: [Expedition 27, visitingShuttleMission, STS-134]
-
A.
associatedShuttleMission
chosen
Indicates that there is a relationship linking something (e.g., an object, event, or record) to a specific space shuttle mission with which it is connected or involved.
-
B.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
C.
shuttleOperation
Indicates that one entity operates, manages, or provides shuttle transportation service for another entity or between specified locations.
-
D.
spaceStationExpedition
Indicates a mission or expedition undertaken to travel to, work on, or return from a space station.
-
E.
hasShuttleBay
Indicates that an entity possesses or is equipped with a shuttle bay as part of its structure or facilities.
- 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_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:03 a.m.