Triple
T10502171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servicing Mission 4 |
E247697
|
entity |
| Predicate | wasFinal |
P33890
|
FINISHED |
| Object | last Space Shuttle mission to Hubble Space Telescope |
—
|
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: last Space Shuttle mission to Hubble Space Telescope | Statement: [Servicing Mission 4, wasFinal, last Space Shuttle mission to Hubble Space Telescope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFinal Context triple: [Servicing Mission 4, wasFinal, last Space Shuttle mission to Hubble Space Telescope]
-
A.
wasLast
chosen
Indicates that one entity occurred or appeared after all others in a sequence, making it the final item or event.
-
B.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
C.
finalHeld
Indicates that an entity ultimately retains possession or control of another entity at the conclusion of a process or event.
-
D.
finalPassing
Indicates that an entity successfully completes or passes a final evaluation, test, or stage in a process.
-
E.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099c6a848190bf1d5361e9e61108 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.