Triple
T6175300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M44 |
E137801
|
entity |
| Predicate | containsRedGiants |
P61260
|
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: [M44, containsRedGiants, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRedGiants Context triple: [M44, containsRedGiants, true]
-
A.
containsDwarfSpheroidalGalaxies
Indicates that the subject spatially includes one or more dwarf spheroidal galaxies within its extent.
-
B.
containsDwarfGalaxies
Indicates that one astronomical object or region includes one or more dwarf galaxies within its boundaries or extent.
-
C.
hasNotableGiant
Indicates that an entity is associated with or characterized by a particularly large or prominent example of something.
-
D.
containsStellarPopulation
chosen
Indicates that one astronomical object includes or encompasses a group of stars as part of its stellar content.
-
E.
stellarPopulation
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.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc55b5c819084482b735771c9a8 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.