Triple
T1416594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronis (Hyad) |
E31931
|
entity |
| Predicate | celestialCategory |
P9991
|
FINISHED |
| Object | star in open cluster |
—
|
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: star in open cluster | Statement: [Coronis (Hyad), celestialCategory, star in open cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celestialCategory Context triple: [Coronis (Hyad), celestialCategory, star in open cluster]
-
A.
astronomicalType
chosen
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
B.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
astronomicalCharacteristic
Indicates that one entity has a specific astronomical property, feature, or attribute in relation to another entity.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
constellationFamily
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
- 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_69a49919a994819086528951bc224775 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c403ccdc8190b2a5fda037b6ea34 |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.