Triple
T18842514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 24398 |
E460830
|
entity |
| Predicate | hasSurfaceGravityLogG |
P69906
|
FINISHED |
| Object | about 2.9 |
—
|
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: about 2.9 | Statement: [HD 24398, hasSurfaceGravityLogG, about 2.9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurfaceGravityLogG Context triple: [HD 24398, hasSurfaceGravityLogG, about 2.9]
-
A.
hasSurfaceGravityLogg
chosen
Indicates the logarithm of the object's surface gravitational acceleration, typically measured in cgs units (log g).
-
B.
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.
-
C.
meanSurfaceGravity_m_per_s2
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
D.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
E.
hasSpecificGravity
Indicates that one entity has a specific gravity value equal to or characteristic of another entity or reference substance.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8eb32548190b2313e877f6ff179 |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.