Triple
T20576488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO 351-30 |
E505229
|
entity |
| Predicate | dominantStellarAge_Gyr |
P103744
|
FINISHED |
| Object | >10 |
—
|
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: >10 | Statement: [ESO 351-30, dominantStellarAge_Gyr, >10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantStellarAge_Gyr Context triple: [ESO 351-30, dominantStellarAge_Gyr, >10]
-
A.
stellarPopulationAge
Indicates the age of a group of stars that formed together within a stellar system or region.
-
B.
hasDominantOldStellarPopulation
chosen
Indicates that an astronomical object’s stellar content is primarily composed of older stars, which dominate its overall stellar population.
-
C.
hostStarAge
Indicates the age of the star that serves as the host in the relationship or system being described.
-
D.
estimatedAgeInMillionsOfYears
Indicates the approximate age of something expressed in units of millions of years.
-
E.
dominantGalaxy
Indicates that one galaxy exerts a dominant influence or control over another galaxy, such as through gravitational effects or hierarchical structure within a system.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a90af3608190955d2c7950726178 |
completed | April 20, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.