Triple
T23740747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance |
E586663
|
entity |
| Predicate | artificialGravityMethod |
P114023
|
FINISHED |
| Object | centrifugal force from rotation |
—
|
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: centrifugal force from rotation | Statement: [Endurance, artificialGravityMethod, centrifugal force from rotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artificialGravityMethod Context triple: [Endurance, artificialGravityMethod, centrifugal force from rotation]
-
A.
hasArtificialGravity
chosen
Indicates that an environment, structure, or vehicle possesses a system that generates gravity-like forces for its occupants.
-
B.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
C.
hasTypicalSurfaceGravity
Indicates that an entity possesses a surface gravity value that falls within the normal or expected range for its class or category.
-
D.
gravityFieldStudiedBy
Indicates that a gravity field is the subject of study or analysis by a particular agent or entity.
-
E.
gravityEffect
Indicates the influence one entity’s gravitational force has on another, such as causing attraction, acceleration, or changes in motion.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad61d908190a0a8493bbba95d49 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.