Triple
T28880702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasFinalBlackHoleMass |
P193832
|
FINISHED |
| Object | 53.2 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: 53.2 solar masses | Statement: [GW170814, hasFinalBlackHoleMass, 53.2 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalBlackHoleMass Context triple: [GW170814, hasFinalBlackHoleMass, 53.2 solar masses]
-
A.
secondaryBlackHoleMass
Indicates the mass of the secondary (less massive) black hole in a binary or multi–black-hole system.
-
B.
hasSupermassiveBlackHole
Indicates that an astronomical object, such as a galaxy, contains or is associated with a supermassive black hole.
-
C.
massOfCentralBlackHole
Indicates the quantitative amount of mass possessed by the central black hole in a given system or context.
-
D.
associatedBlackHole
Indicates a relationship where one entity is linked or connected to a specific black hole, typically as its corresponding or related black hole.
-
E.
hasSupermassiveBlackHoleMeasurementMethod
Indicates the method or technique used to determine or measure the properties or presence of a supermassive black hole.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 28, 2026, 7:43 a.m.