Triple
T18298888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Neill cylinder |
E438302
|
entity |
| Predicate | artificialGravityOn |
P114023
|
FINISHED |
| Object | inner surface |
—
|
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: inner surface | Statement: [O'Neill cylinder, artificialGravityOn, inner surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artificialGravityOn Context triple: [O'Neill cylinder, artificialGravityOn, inner surface]
-
A.
hasArtificialGravity
chosen
Indicates that an environment, structure, or vehicle possesses a system that generates gravity-like forces for its occupants.
-
B.
gravityAffected
Indicates that an entity is subject to the force of gravity, causing it to accelerate or move in response to gravitational pull.
-
C.
gravityEnvironment
Indicates the gravitational conditions or field in which an entity exists or an action occurs.
-
D.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
E.
hasSurfaceGravity
Indicates that one entity possesses a specific gravitational acceleration at its surface, typically measured as the strength of gravity experienced at or near that surface.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017d96588190ac1e326803142976 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.