Triple
T21552253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylab Multiple Docking Adapter |
E531791
|
entity |
| Predicate | usedOnMissionDuration |
P144209
|
FINISHED |
| Object | 1973–1974 |
—
|
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: 1973–1974 | Statement: [Skylab Multiple Docking Adapter, usedOnMissionDuration, 1973–1974]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnMissionDuration Context triple: [Skylab Multiple Docking Adapter, usedOnMissionDuration, 1973–1974]
-
A.
timeOfMission
Indicates the specific time or period during which a mission takes place or is scheduled.
-
B.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
C.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
D.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
E.
missionDurationCapability
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
- F. None of above. chosen
Provenance (4 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.