Triple
T4531617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andromeda IV |
E106310
|
entity |
| Predicate | hasStellarPopulation |
P22291
|
FINISHED |
| Object | 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: old stars | Statement: [Andromeda IV, hasStellarPopulation, old stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStellarPopulation Context triple: [Andromeda IV, hasStellarPopulation, old stars]
-
A.
stellarPopulation
chosen
Indicates a relationship where one entity represents the group or distribution of stars (stellar population) associated with another entity, such as a galaxy or region of space.
-
B.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
C.
hasBrightStar
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
-
D.
hostStarMetallicityEffect
Indicates how the metallicity (elemental composition) of a host star influences the properties, formation, or occurrence of its orbiting planets.
-
E.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.