Triple
T1000520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis Major Dwarf Galaxy |
E21591
|
entity |
| Predicate | stellarPopulation |
P22291
|
FINISHED |
| Object | predominantly old stars |
—
|
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: predominantly old stars | Statement: [Canis Major Dwarf Galaxy, stellarPopulation, predominantly old stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stellarPopulation Context triple: [Canis Major Dwarf Galaxy, stellarPopulation, predominantly old stars]
-
A.
starSystem
Indicates a relationship where an astronomical object or location belongs to, is part of, or is located within a particular star system.
-
B.
approximateStellarCount
Indicates an estimated or rough number of stars associated with a given astronomical object or region.
-
C.
starCount
Indicates the number of stars associated with an entity, typically representing a rating, quality level, or count of starred items.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
cataloguedAsStar
Indicates that an object has been classified and recorded specifically as a star in a catalog or database.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b3a02ea481909555cf5b7bed0d9a |
completed | March 1, 2026, 9:46 p.m. |
Created at: March 1, 2026, 7:41 p.m.