Triple
T2344813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoebe |
E45105
|
entity |
| Predicate | gravity |
P28552
|
FINISHED |
| Object | very low surface gravity |
—
|
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: very low surface gravity | Statement: [Phoebe, gravity, very low surface gravity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravity Context triple: [Phoebe, gravity, very low surface gravity]
-
A.
interactsGravitationallyWith
Indicates that one entity exerts a gravitational influence on, and is influenced by, another entity, according to the laws of gravity.
-
B.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
-
C.
meanSurfaceGravity_m_per_s2
chosen
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
D.
weight
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
E.
equatorialGravity
Indicates the strength or value of gravitational acceleration measured at an object's equator.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.