Triple
T29577765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conshelf II |
E753490
|
entity |
| Predicate | secondCrewMissionDuration |
P146820
|
FINISHED |
| Object | 3 weeks |
—
|
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: 3 weeks | Statement: [Conshelf II, secondCrewMissionDuration, 3 weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondCrewMissionDuration Context triple: [Conshelf II, secondCrewMissionDuration, 3 weeks]
-
A.
secondCrewedMission
chosen
Indicates that the mission is the second one to carry a crew.
-
B.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
C.
timeOfMission
Indicates the specific time or period during which a mission takes place or is scheduled.
-
D.
secondISSLongDurationMissionEnd
Indicates the point in time when an entity’s second long-duration mission aboard the International Space Station concludes.
-
E.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 6:04 p.m.