Triple
T29577812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conshelf II habitat |
E753491
|
entity |
| Predicate | experimentalDuration |
P40756
|
FINISHED |
| Object | about one month |
—
|
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 one month | Statement: [Conshelf II habitat, experimentalDuration, about one month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experimentalDuration Context triple: [Conshelf II habitat, experimentalDuration, about one month]
-
A.
actualDuration
chosen
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
B.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
C.
evaDuration
Indicates the length of time that an extravehicular activity (EVA) lasts or is scheduled to last.
-
D.
eraDuration
Indicates the length of time that a particular era or period spans.
-
E.
durationInitial
Indicates the initial length of time associated with an event, state, or process at its starting point.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:04 p.m.