Triple
T21314238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4649 |
E525422
|
entity |
| Predicate | hasSupermassiveBlackHoleMass |
P20365
|
FINISHED |
| Object | about 4.5 billion solar masses |
—
|
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: about 4.5 billion solar masses | Statement: [NGC 4649, hasSupermassiveBlackHoleMass, about 4.5 billion solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupermassiveBlackHoleMass Context triple: [NGC 4649, hasSupermassiveBlackHoleMass, about 4.5 billion solar masses]
-
A.
hasSupermassiveBlackHole
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
B.
massOfCentralBlackHole
chosen
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
C.
hasSupermassiveBlackHoleMeasurementMethod
Indicates the method or technique used to determine or measure the properties or presence of a supermassive black hole.
-
D.
hasDarkMatterHalo
Indicates that an astronomical object is surrounded by or associated with a dark matter halo.
-
E.
isMoreMassiveThanSun
Indicates that the subject has a greater mass than the Sun.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcd4d5c8190856ddd34bb15d735 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:28 p.m.