Triple
T1617642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-61 |
E34755
|
entity |
| Predicate | totalEVATime |
P26367
|
FINISHED |
| Object | 35 hours 28 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: 35 hours 28 minutes | Statement: [STS-61, totalEVATime, 35 hours 28 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEVATime Context triple: [STS-61, totalEVATime, 35 hours 28 minutes]
-
A.
evaDuration
chosen
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
B.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
C.
timeEquivalentOf
Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
-
D.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fef600c819080fe75c42c8e6dac |
completed | March 5, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69a907c52a548190b648a31ea306dd5b |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.