Triple
T14479950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-51-I |
E359072
|
entity |
| Predicate | shuttleMissionNumber |
P26361
|
FINISHED |
| Object | 20th Space Shuttle mission overall |
—
|
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: 20th Space Shuttle mission overall | Statement: [STS-51-I, shuttleMissionNumber, 20th Space Shuttle mission overall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shuttleMissionNumber Context triple: [STS-51-I, shuttleMissionNumber, 20th Space Shuttle mission overall]
-
A.
missionNumber
chosen
Indicates the identifying number assigned to a specific mission within a sequence or set of missions.
-
B.
orbiterFlightNumber
Indicates the specific flight identification number assigned to an orbiter mission.
-
C.
spaceShuttleFlight
Indicates a specific mission or journey undertaken by a space shuttle between launch and landing.
-
D.
missionID
Indicates a unique identifier that associates an entity with a specific mission or operation.
-
E.
spaceMissionsFlown
Indicates the number or specific instances of space missions that an entity has participated in or carried out.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924a576c819098351efabdb779b1 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.