Triple
T4619060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaus Australis |
E100934
|
entity |
| Predicate | hasRadius_solarRadius |
P57022
|
FINISHED |
| Object | about 6.8 |
—
|
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 6.8 | Statement: [Kaus Australis, hasRadius_solarRadius, about 6.8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadius_solarRadius Context triple: [Kaus Australis, hasRadius_solarRadius, about 6.8]
-
A.
hasMeanRadius
Indicates that an entity possesses a specified average radius measurement, typically representing the mean distance from its center to its surface.
-
B.
hasMeanDistanceFromSun
Indicates that an entity (typically a celestial body) is characterized by a specific average distance from the Sun.
-
C.
radiusRelativeToJupiter
Indicates that the radius of one object is expressed as a value relative to the radius of Jupiter.
-
D.
luminosityRelativeToSun
Indicates how bright an object is compared to the Sun, expressed as a ratio of their luminosities.
-
E.
hasPolarDiameter_km
Indicates the length of an object's diameter measured from pole to pole, expressed in kilometers.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.