Triple
T5940539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shapley Supercluster |
E132154
|
entity |
| Predicate | hasApproximateMass |
P7301
|
FINISHED |
| Object | of order 10^16 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: of order 10^16 solar masses | Statement: [Shapley Supercluster, hasApproximateMass, of order 10^16 solar masses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateMass Context triple: [Shapley Supercluster, hasApproximateMass, of order 10^16 solar masses]
-
A.
approximateMass
chosen
Indicates that one entity has a mass value that is an estimate or close approximation of the mass of another entity.
-
B.
hasMass_kg
Indicates that an entity possesses a specific mass measured in kilograms.
-
C.
approximateWeightInPounds
Indicates the estimated weight of an entity expressed in pounds, rather than an exact measured value.
-
D.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
E.
obtainsMassVia
Indicates that an entity acquires its mass through a specified process, mechanism, or interaction.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.