Triple
T28249072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 244 |
E712265
|
entity |
| Predicate | radiusOfPrimary_solarRadius |
P57022
|
FINISHED |
| Object | about 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: about 1.7 | Statement: [Gliese 244, radiusOfPrimary_solarRadius, about 1.7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiusOfPrimary_solarRadius Context triple: [Gliese 244, radiusOfPrimary_solarRadius, about 1.7]
-
A.
hasRadius_solarRadius
chosen
Indicates that an entity has a radius whose value is expressed in units of the Sun’s radius.
-
B.
hasRadiusOfPrimary
Indicates that an entity (typically an orbiting body or system) is associated with a primary object whose radius is specified by the related value or entity.
-
C.
sizeRelativeToSun
Indicates how the size of one entity compares to the size of the Sun.
-
D.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
E.
meanOrbitalRadius_km
Indicates the average distance, measured in kilometers, between an orbiting body and the center of the object it orbits.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:03 p.m.