Triple
T37205544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abell 2151 |
E922159
|
entity |
| Predicate | hasDominantGalaxyType |
P148007
|
FINISHED |
| Object | late-type galaxies |
—
|
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: late-type galaxies | Statement: [Abell 2151, hasDominantGalaxyType, late-type galaxies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDominantGalaxyType Context triple: [Abell 2151, hasDominantGalaxyType, late-type galaxies]
-
A.
dominantGalaxyType
chosen
Indicates the type of galaxy that is most prevalent or characteristic within a given region, system, or sample.
-
B.
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.
-
C.
hasGalaxyType
Indicates that a galaxy is classified as belonging to a specific morphological or structural type.
-
D.
hasCentralGalaxy
Indicates that a galaxy cluster or group possesses a specific galaxy that occupies the central, dominant position within it.
-
E.
hasGalacticObjectType
Indicates that an entity is associated with, or classified as, a specific type of galactic object.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:15 p.m.