Triple
T23244298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipparcos Catalogue |
E581539
|
entity |
| Predicate | containsVariableStarSolutions |
P135149
|
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, containsVariableStarSolutions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVariableStarSolutions Context triple: [Hipparcos Catalogue, containsVariableStarSolutions, yes]
-
A.
containsVariableStars
chosen
Indicates that the subject includes one or more stars whose brightness changes over time (variable stars).
-
B.
hasVariableStarDesignation
Indicates that an entity is assigned a specific variable star designation in an astronomical naming system.
-
C.
numberOfVariableStars
Indicates the count of variable stars associated with or present in a given context or entity.
-
D.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
E.
variableStarType
Indicates the specific classification of variability that characterizes a variable star’s changing brightness.
- 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_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. |
Created at: April 17, 2026, 4:10 p.m.