Triple
T28943543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW150914 |
E730519
|
entity |
| Predicate | primaryBlackHoleMass |
P199190
|
FINISHED |
| Object | about 36 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 36 solar masses | Statement: [GW150914, primaryBlackHoleMass, about 36 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBlackHoleMass Context triple: [GW150914, primaryBlackHoleMass, about 36 solar masses]
-
A.
secondaryBlackHoleMass
Indicates the mass of the secondary (less massive) black hole in a binary or multi–black-hole system.
-
B.
hasPrimaryBlackHoleMass
chosen
Indicates that an entity (such as a system or object) is associated with a specific value representing the mass of its primary 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.
hasFinalBlackHoleMass
Indicates the resulting mass of a black hole after a process or event has completed.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: April 28, 2026, 8:38 a.m.