Triple
T4531709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M81 Group |
E106311
|
entity |
| Predicate | containsDwarfSpheroidalGalaxies |
P57290
|
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: [M81 Group, containsDwarfSpheroidalGalaxies, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDwarfSpheroidalGalaxies Context triple: [M81 Group, containsDwarfSpheroidalGalaxies, true]
-
A.
isSatelliteGalaxyOf
Indicates that one galaxy orbits and is gravitationally bound to another, larger host galaxy as its satellite.
-
B.
galacticComponent
Indicates that one entity is a structural part or subregion of a galaxy, such as a disk, bulge, halo, or similar galactic subdivision.
-
C.
numberOfGlobularClusters
Indicates the quantitative relationship specifying how many globular clusters are associated with a given astronomical object or system.
-
D.
hasDwarfPlanet
Indicates that one entity possesses or is associated with a dwarf planet as part of its system or domain.
-
E.
associatedGlobularCluster
Indicates that one entity is linked or connected to a particular globular cluster in an astronomically relevant way.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.