Triple
T32141779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burkert profile |
E820923
|
entity |
| Predicate | massProfile |
P150638
|
FINISHED |
| Object | M(r) = 4π ∫₀ʳ ρ(r′) r′² dr′ |
—
|
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: M(r) = 4π ∫₀ʳ ρ(r′) r′² dr′ | Statement: [Burkert profile, massProfile, M(r) = 4π ∫₀ʳ ρ(r′) r′² dr′]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massProfile Context triple: [Burkert profile, massProfile, M(r) = 4π ∫₀ʳ ρ(r′) r′² dr′]
-
A.
clusterMass
Indicates the total mass associated with a given cluster, typically aggregating the masses of its constituent elements or members.
-
B.
massFunction
chosen
Indicates a relationship that assigns a quantitative mass value or distribution to an entity or set of entities.
-
C.
massToLightRatio
Indicates the relationship between an object's total mass and its luminosity, expressing how much mass corresponds to each unit of emitted light.
-
D.
stellarMass
Indicates the amount of mass an astronomical object has that is contained in its stars.
-
E.
massContribution
Indicates that an entity contributes some or all of its mass to another entity or system.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9aed8c881908214b59cb895fa65 |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.