Triple

T19686099
Position Surface form Disambiguated ID Type / Status
Subject Milky Way globular cluster system E472714 entity
Predicate hasLuminosityFunctionPeak P77981 FINISHED
Object absolute V magnitude around −7.4 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: absolute V magnitude around −7.4 | Statement: [Milky Way globular cluster system, hasLuminosityFunctionPeak, absolute V magnitude around −7.4]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLuminosityFunctionPeak
Context triple: [Milky Way globular cluster system, hasLuminosityFunctionPeak, absolute V magnitude around −7.4]
  • A. hasPeak
    Indicates that something possesses or contains a highest point, summit, or maximum value.
  • B. hasPeakAssociated
    Indicates that one entity is linked or related to a specific peak (such as a summit or maximum point) associated with it.
  • C. hasLowLuminosity
    Indicates that an entity emits relatively little light or energy compared to a typical or reference level.
  • D. hasPeakAround chosen
    Indicates that something exhibits a maximum value, intensity, or prominence in the vicinity of a specified point, range, or condition.
  • E. hasPeakOver
    Indicates that one entity’s peak (such as a maximum value, height, or intensity) exceeds that of another entity.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6420c3f50819082b64b1fa4335e56 completed April 20, 2026, 3:11 p.m.
PD Predicate disambiguation batch_69e53039ea808190a9106a53f564ab92 completed April 19, 2026, 7:42 p.m.
Created at: April 10, 2026, 1:45 p.m.