Triple
T6287300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 21421 |
E140930
|
entity |
| Predicate | isPrimaryStandardStar |
P34280
|
FINISHED |
| Object | yes, for spectral type K5 III |
—
|
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, for spectral type K5 III | Statement: [HIP 21421, isPrimaryStandardStar, yes, for spectral type K5 III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryStandardStar Context triple: [HIP 21421, isPrimaryStandardStar, yes, for spectral type K5 III]
-
A.
isMainSequenceStar
Indicates that a star is currently in the main, hydrogen-burning phase of its stellar evolution.
-
B.
isPrimaryStarOf
Indicates that a star serves as the main or central stellar object in relation to a specified system, object, or context.
-
C.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
-
D.
isVariableStar
Indicates that an astronomical object exhibits intrinsic brightness variations over time, classifying it as a variable star.
-
E.
isStandardOf
chosen
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063ff9f74819088dc603f56fc930c |
completed | March 22, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69c0560a0270819098ad2785b91e8f39 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:26 p.m.