Triple
T11316907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSR B1913+16 |
E267990
|
entity |
| Predicate | totalSystemMass |
P22401
|
FINISHED |
| Object | about 2.83 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 2.83 solar masses | Statement: [PSR B1913+16, totalSystemMass, about 2.83 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSystemMass Context triple: [PSR B1913+16, totalSystemMass, about 2.83 solar masses]
-
A.
totalMass_solarMasses
chosen
Indicates the total mass of an object or system expressed in units of solar masses (multiples of the Sun’s mass).
-
B.
fractionOfSolarSystemMass
Indicates the proportion of the total mass of the Solar System that is accounted for by a given entity.
-
C.
totalSystemLength
Indicates the complete measured length of an entire system, aggregating all its relevant components or segments.
-
D.
dynamicalMass_solarMasses
Indicates the dynamical mass of an object or system expressed in units of the Sun’s mass.
-
E.
spacecraftMass
Indicates the mass value associated with a spacecraft in a given context.
- 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.