Triple
T23782995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 21432 |
E587867
|
entity |
| Predicate | hasAstrometricSource |
P153921
|
FINISHED |
| Object | Hipparcos mission |
—
|
NE NERFINISHED |
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: Hipparcos mission | Statement: [HIP 21432, hasAstrometricSource, Hipparcos mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstrometricSource Context triple: [HIP 21432, hasAstrometricSource, Hipparcos mission]
-
A.
astrometricAccuracy
Indicates the degree of precision with which the position and motion of an astronomical object are measured or determined.
-
B.
hasHipparcosCatalog
Indicates that an astronomical object is associated with an entry in the Hipparcos star catalog.
-
C.
hasStarCatalogIdentifier
Indicates that an astronomical object is associated with a specific identifier assigned to it in a star catalog.
-
D.
hasSIMBADIdentifier
Indicates that an astronomical object is associated with a specific identifier in the SIMBAD astronomical database.
-
E.
astrometricSolutionFor
Indicates that one entity is an astrometric solution (a calculated position and motion) derived for another entity, typically an observed astronomical source.
- 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_69e2490f4ad48190b690878eec3596c6 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c62ea9c0819083544822267d3215 |
completed | April 29, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15ed138f88190a8ae555422978908 |
completed | April 29, 2026, 1:28 a.m. |
Created at: April 17, 2026, 7:16 p.m.