Triple
T10502157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servicing Mission 4 |
E247697
|
entity |
| Predicate | EVAcumulativeTime |
P43134
|
FINISHED |
| Object | about 36 hours |
—
|
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: about 36 hours | Statement: [Servicing Mission 4, EVAcumulativeTime, about 36 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAcumulativeTime Context triple: [Servicing Mission 4, EVAcumulativeTime, about 36 hours]
-
A.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
B.
endTimeDetail
Indicates the specific or refined information about when an event, action, or state concludes.
-
C.
durationTotal
chosen
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
D.
periodInPowerEnd
Indicates the point in time when an entity’s tenure or period in power comes to an end.
-
E.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
- 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.