Triple
T4619057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaus Australis |
E100934
|
entity |
| Predicate | hasParallax_mas |
P24833
|
FINISHED |
| Object | 22.34 |
—
|
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: 22.34 | Statement: [Kaus Australis, hasParallax_mas, 22.34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParallax_mas Context triple: [Kaus Australis, hasParallax_mas, 22.34]
-
A.
parallax_mas
chosen
Indicates the apparent shift in an object's position on the sky, measured in milliarcseconds, due to the observer’s change in viewpoint (typically Earth’s orbit around the Sun).
-
B.
parallax
Indicates the apparent shift in an object’s position relative to a background when observed from two different viewpoints or at two different times.
-
C.
parallaxAccuracy
Indicates the degree of precision or reliability associated with a measured parallax value.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasMessierNumber
Indicates that an astronomical object is identified by a specific catalog entry in the Messier catalog.
- 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_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. |
Created at: March 20, 2026, 1:12 p.m.