Triple
T18771928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 24912 |
E459034
|
entity |
| Predicate | parallaxMilliarcseconds |
P24833
|
FINISHED |
| Object | 3.01 |
—
|
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: 3.01 | Statement: [HD 24912, parallaxMilliarcseconds, 3.01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parallaxMilliarcseconds Context triple: [HD 24912, parallaxMilliarcseconds, 3.01]
-
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.
meanParallaxUncertainty
Indicates the average level of uncertainty or error associated with measured parallax values in a dataset or observation set.
-
C.
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.
-
D.
parallaxZeroPointOffset
Indicates a systematic offset or bias in the reference (zero) point used to measure parallax values.
-
E.
parallaxAccuracy
Indicates the degree of precision or reliability associated with a measured parallax value.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59336a6b08190819595a55177264e |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.