Triple

T23527549
Position Surface form Disambiguated ID Type / Status
Subject Coma Cluster E576473 entity
Predicate hasLuminosityFunction P153111 FINISHED
Object well-studied 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: well-studied | Statement: [Coma Cluster, hasLuminosityFunction, well-studied]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLuminosityFunction
Context triple: [Coma Cluster, hasLuminosityFunction, well-studied]
  • A. hasLuminosityOfPrimary
    Indicates that one entity has the same luminosity value or luminosity classification as the primary entity in a given system or context.
  • B. hasLowLuminosity
    Indicates that an entity emits relatively little light or energy compared to a typical or reference level.
  • C. hasLuminosityOfSecondary
    Indicates that one entity has the luminosity value or brightness level associated with a secondary object in a system or relationship.
  • D. hasLumen
    Indicates that one entity possesses or is characterized by a specific luminous intensity or light output measured in lumens.
  • E. hasInitialMassFunction
    Indicates that an astronomical object or system is associated with a specific initial mass function describing the distribution of stellar masses at their formation.
  • F. None of above. chosen

Provenance (4 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_69e245f5a8848190a2ba42e271c6c31f completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1ac74be1881909161b94aa611188a completed April 29, 2026, 7 a.m.
PD Predicate disambiguation batch_69f1189d75b48190a1c01928a993c9fb completed April 28, 2026, 8:29 p.m.
PDg Predicate description generation batch_69f12760784c8190aaeff002ef31febe completed April 28, 2026, 9:32 p.m.
Created at: April 17, 2026, 6:09 p.m.