Triple
T26987008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 144 |
E679759
|
entity |
| Predicate | hasAstrometricData |
P153921
|
FINISHED |
| Object | measured by Hipparcos mission |
—
|
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: measured by Hipparcos mission | Statement: [Gliese 144, hasAstrometricData, measured by Hipparcos mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstrometricData Context triple: [Gliese 144, hasAstrometricData, measured by Hipparcos mission]
-
A.
hasAstrometricSource
chosen
Indicates that an entity is associated with a source providing astrometric measurements or positional data.
-
B.
astrometricAccuracy
Indicates the degree of precision with which the position and motion of an astronomical object are measured or determined.
-
C.
containsAstrometricQualityFlags
Indicates that an entity includes specific astrometric quality flags characterizing the reliability or conditions of its positional or motion measurements.
-
D.
hasPhotometry
Indicates that an entity possesses or is associated with photometric data or measurements.
-
E.
hasHipparcosCatalog
Indicates that an astronomical object is associated with an entry in the Hipparcos star 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 6:49 a.m.