Triple
T6246197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altarf |
E139726
|
entity |
| Predicate | hasSurfaceGravity_logg |
P2024
|
FINISHED |
| Object | 1.7 |
—
|
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: 1.7 | Statement: [Altarf, hasSurfaceGravity_logg, 1.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceGravity_logg Context triple: [Altarf, hasSurfaceGravity_logg, 1.7]
-
A.
hasSurfaceGravity
chosen
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.
-
B.
meanSurfaceGravity_m_per_s2
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
C.
surfaceGravityAnomaly
Indicates a deviation of an object's local surface gravitational acceleration from a reference or expected gravitational field.
-
D.
equatorialGravity
Indicates the strength or value of gravitational acceleration measured at an object's equator.
-
E.
hasRegolithDepth
Indicates the depth or thickness of a layer of regolith present on a surface or object.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631d9e648190a59ab4001f506424 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.