Triple
T28880720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GW170814 |
E732408
|
entity |
| Predicate | hasChirpMass |
P182400
|
FINISHED |
| Object | ~24 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: ~24 solar masses | Statement: [GW170814, hasChirpMass, ~24 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChirpMass Context triple: [GW170814, hasChirpMass, ~24 solar masses]
-
A.
hasApproximateMassRatio
Indicates that one entity’s mass is approximately proportional to, or in a specified ratio with, the mass of another entity, within an accepted tolerance.
-
B.
hasCombinedApparentMagnitude
Indicates that a group of astronomical objects, when considered together, have a specific total apparent brightness as seen by an observer.
-
C.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
-
D.
hasVirialMass
Indicates that an entity possesses a mass value determined via the virial theorem, typically inferred from its internal motions or dynamics.
-
E.
hasLowMass
Indicates that the subject possesses a relatively small amount of mass compared to a given standard or reference.
- 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_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: April 28, 2026, 7:43 a.m.