Triple
T9399481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Botany Bay |
E226430
|
entity |
| Predicate | stasisTechnology |
P88727
|
FINISHED |
| Object | sleeper pods |
—
|
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: sleeper pods | Statement: [SS Botany Bay, stasisTechnology, sleeper pods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stasisTechnology Context triple: [SS Botany Bay, stasisTechnology, sleeper pods]
-
A.
stabilizedBy
Indicates that an entity’s state, structure, or behavior is made more steady, secure, or resistant to change through the influence or support of another entity.
-
B.
stabilityDescription
Indicates how stable, consistent, or enduring the relationship, condition, or state between the entities is over time.
-
C.
stabilizationOutcome
Indicates the result or state achieved after a stabilization process has been applied to something.
-
D.
servedAsTechnologicalBasisFor
Indicates that one technology, system, or method functioned as the foundational platform or enabling precursor upon which another technology was developed or built.
-
E.
spaceStationType
Indicates the specific functional or structural category to which a space station belongs (e.g., research, military, commercial).
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51556fc08190b8ff8190a1485a3a |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:46 p.m.