Triple
T33094606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-39 |
E846875
|
entity |
| Predicate | shuttleDiscoveryFlightNumber |
P38973
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [STS-39, shuttleDiscoveryFlightNumber, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shuttleDiscoveryFlightNumber Context triple: [STS-39, shuttleDiscoveryFlightNumber, 12]
-
A.
spaceShuttleFlight
Indicates a specific mission or journey undertaken by a space shuttle between launch and landing.
-
B.
orbiterFlightNumber
chosen
Indicates the specific flight identification number assigned to an orbiter mission.
-
C.
vehicleFlightNumber
Indicates the specific flight number associated with a given vehicle (such as an aircraft) in an air transport context.
-
D.
orbitFirstReachedFlightNumber
Indicates the flight number of the first mission or launch by which an object successfully reached orbit.
-
E.
nextShuttleFlightAfterDisaster
Indicates the first shuttle flight that took place after a specified disaster event.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a7c6348190bc2f40bdf6597288 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.