Triple

T32141781
Position Surface form Disambiguated ID Type / Status
Subject Burkert profile E820923 entity
Predicate coreDensityRadiusProduct P61029 FINISHED
Object approximately constant across galaxies (empirical claim) 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: approximately constant across galaxies (empirical claim) | Statement: [Burkert profile, coreDensityRadiusProduct, approximately constant across galaxies (empirical claim)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coreDensityRadiusProduct
Context triple: [Burkert profile, coreDensityRadiusProduct, approximately constant across galaxies (empirical claim)]
  • A. clusterDensity
    Indicates the degree to which elements within a cluster are closely packed or concentrated relative to its size or volume.
  • B. coreRadius_pc
    Indicates the radius of the central or core region of an object or system, measured in parsecs.
  • C. givesDensityOf
    Indicates that one entity provides or specifies the density value of another entity.
  • D. hasCentralDensity chosen
    Indicates that an entity possesses a specified value for its density at the central or core region.
  • E. hasMeanDensity
    Indicates that one entity possesses a specified average mass per unit volume (mean density).
  • 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.