Triple
T5410509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgo Cluster |
E121000
|
entity |
| Predicate | centralBlackHoleMassEstimate |
P20365
|
FINISHED |
| Object | about 6.5×10^9 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 6.5×10^9 solar masses | Statement: [Virgo Cluster, centralBlackHoleMassEstimate, about 6.5×10^9 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralBlackHoleMassEstimate Context triple: [Virgo Cluster, centralBlackHoleMassEstimate, about 6.5×10^9 solar masses]
-
A.
massOfCentralBlackHole
chosen
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
B.
centralBlackHoleName
Indicates the designated name assigned to a galaxy’s central black hole.
-
C.
hasSupermassiveBlackHole
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
D.
dynamicalMass_solarMasses
Indicates the dynamical mass of an object or system expressed in units of the Sun’s mass.
-
E.
roleInBlackHoles
Indicates the specific function, influence, or involvement an entity has in the formation, behavior, or study of black holes.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87985ee0819092a9a5cd6a948138 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.