Triple
T5201971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SagDEG |
E117412
|
entity |
| Predicate | hasDarkMatterDominance |
P22856
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SagDEG, hasDarkMatterDominance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDarkMatterDominance Context triple: [SagDEG, hasDarkMatterDominance, true]
-
A.
darkMatterDominated
chosen
Indicates that the system or region is primarily influenced or governed by dark matter rather than by ordinary (baryonic) matter.
-
B.
hasDarkMatterHalo
Indicates that an astronomical object is surrounded by or associated with a dark matter halo.
-
C.
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.
-
D.
containsDwarfSpheroidalGalaxies
Indicates that the subject spatially includes one or more dwarf spheroidal galaxies within its extent.
-
E.
containsDwarfGalaxies
Indicates that one astronomical object or region includes one or more dwarf galaxies within its boundaries or extent.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.