Triple
T21818830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Cephei |
E538669
|
entity |
| Predicate | hasTypicalSurfaceGravity |
P145791
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Beta Cephei, hasTypicalSurfaceGravity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSurfaceGravity Context triple: [Beta Cephei, hasTypicalSurfaceGravity, high]
-
A.
meanSurfaceGravity_m_per_s2
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
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.
hasSurfaceGravityLogg
Indicates the logarithm of the object's surface gravitational acceleration, typically measured in cgs units (log g).
-
D.
gravityOfBody
Indicates the gravitational influence or field produced by a specific celestial body.
-
E.
hasArtificialGravity
Indicates that an environment, structure, or vehicle possesses a system that generates gravity-like forces for its occupants.
- F. None of above. chosen
Provenance (4 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07ccd0d908190a43af4fcc7d6ca03 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.