Triple
T5951479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biosphere 2 |
E132406
|
entity |
| Predicate | Biosphere 2 mission 1 |
P66948
|
FINISHED |
| Object | 1991–1993 |
—
|
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: 1991–1993 | Statement: [Biosphere 2, Biosphere 2 mission 1, 1991–1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Biosphere 2 mission 1 Context triple: [Biosphere 2, Biosphere 2 mission 1, 1991–1993]
-
A.
hasBiosphere
Indicates that an entity possesses or supports a biosphere, i.e., a region where living organisms and ecological processes exist.
-
B.
orbiterMissionLife
Indicates the duration or expected operational lifetime of an orbiter mission around a target body.
-
C.
ArtemisIVMissionType
Indicates the specific category or classification of the Artemis IV mission based on its planned objectives or operational profile.
-
D.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
E.
missionName
Indicates the designated title or label assigned to a specific 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0335806788190b6488ca8b73f7a63 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 4:02 p.m.