Triple
T2330485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-103 |
E48389
|
entity |
| Predicate | totalEVAtime |
P26367
|
FINISHED |
| Object | 24 hours 33 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: 24 hours 33 minutes | Statement: [STS-103, totalEVAtime, 24 hours 33 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalEVAtime Context triple: [STS-103, totalEVAtime, 24 hours 33 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.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
D.
timeEquivalentOf
Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
-
E.
electrificationUsedBetween
Indicates that an electrification system or method is applied or present along the segment or connection between two entities.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.