Triple
T24334781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 4709 |
E613347
|
entity |
| Predicate | centralBlackHole |
P56992
|
FINISHED |
| Object | supermassive black hole (inferred) |
—
|
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: supermassive black hole (inferred) | Statement: [NGC 4709, centralBlackHole, supermassive black hole (inferred)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralBlackHole Context triple: [NGC 4709, centralBlackHole, supermassive black hole (inferred)]
-
A.
centralBlackHoleName
Indicates the designated name assigned to a galaxy’s central black hole.
-
B.
associatedBlackHole
Indicates a relationship where one entity is linked or connected to a specific black hole, typically as its corresponding or related black hole.
-
C.
hasSupermassiveBlackHole
chosen
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
D.
massOfCentralBlackHole
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f444b08190b9c8e033ff6ee5fc |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:56 a.m.