Triple
T5224947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-120 |
E117961
|
entity |
| Predicate | evaTotalDuration |
P43134
|
FINISHED |
| Object | ~27 hours 14 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: ~27 hours 14 minutes | Statement: [STS-120, evaTotalDuration, ~27 hours 14 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaTotalDuration Context triple: [STS-120, evaTotalDuration, ~27 hours 14 minutes]
-
A.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
B.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
C.
eraDuration
Indicates the length of time that a particular era or period spans.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
actualDuration
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.