Triple
T23244317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos Catalogue |
E581539
|
entity |
| Predicate | containsAstrometricQualityFlags |
P151514
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hipparcos Catalogue, containsAstrometricQualityFlags, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAstrometricQualityFlags Context triple: [Hipparcos Catalogue, containsAstrometricQualityFlags, yes]
-
A.
astrometricAccuracy
Indicates the degree of precision with which the position and motion of an astronomical object are measured or determined.
-
B.
hasAstronomicalCode
Indicates that an entity is associated with a specific astronomical identification code used in celestial catalogs or classification systems.
-
C.
hasPhotometry
Indicates that an entity possesses or is associated with photometric data or measurements.
-
D.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
E.
hasOrbitalUncertainty
Indicates that the orbit of an object is not precisely determined and carries some degree of measurement or prediction uncertainty.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:10 p.m.