Triple
T11316906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR B1913+16 |
E267990
|
entity |
| Predicate | massOfCompanion |
P61262
|
FINISHED |
| Object | about 1.39 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 1.39 solar masses | Statement: [PSR B1913+16, massOfCompanion, about 1.39 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massOfCompanion Context triple: [PSR B1913+16, massOfCompanion, about 1.39 solar masses]
-
A.
hasCompanionStar
Indicates that an astronomical object is gravitationally bound to and forms a system with another star.
-
B.
hasCompanionMagnitude
Indicates that one entity is associated with another entity whose magnitude (such as size, intensity, or value) is being specified or characterized.
-
C.
spectralTypeOfCompanion
Indicates the spectral classification assigned to a companion object in a system, describing the type of its electromagnetic spectrum.
-
D.
dynamicalMass_solarMasses
chosen
Indicates the dynamical mass of an object or system expressed in units of the Sun’s mass.
-
E.
isMoreMassiveThanSun
Indicates that the subject has a greater mass than the Sun.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9c3cf748190987838029d9f7fff |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.