Triple
T32213367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble Servicing Mission 2 |
E822864
|
entity |
| Predicate | totalEvaTime |
P26367
|
FINISHED |
| Object | 33 hours 11 minutes |
—
|
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: 33 hours 11 minutes | Statement: [Hubble Servicing Mission 2, totalEvaTime, 33 hours 11 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEvaTime Context triple: [Hubble Servicing Mission 2, totalEvaTime, 33 hours 11 minutes]
-
A.
evaDuration
chosen
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
B.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
C.
timeOfEvaluation
Indicates the specific time or moment at which an assessment, measurement, or judgment is made about an entity or situation.
-
D.
calculationTime
Indicates the amount of time required to perform or complete a calculation.
-
E.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 12:37 a.m.