Triple

T18594015
Position Surface form Disambiguated ID Type / Status
Subject UGC 6018 E454443 entity
Predicate hasRedshiftFrame P131617 FINISHED
Object local group standard of rest 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: local group standard of rest | Statement: [UGC 6018, hasRedshiftFrame, local group standard of rest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRedshiftFrame
Context triple: [UGC 6018, hasRedshiftFrame, local group standard of rest]
  • A. hasRedshiftRange
    Indicates that there is an associated interval of redshift values within which the entity is observed, valid, or applicable.
  • B. redshiftFrame chosen
    Indicates the reference frame or convention in which a redshift measurement is defined or expressed.
  • C. occursAtRedshift
    Indicates that an event or phenomenon takes place at a specified cosmological redshift value.
  • D. redshift
    Indicates that the observed wavelength of light or other electromagnetic radiation from an object is shifted toward longer (redder) wavelengths, typically due to relative motion away from the observer or cosmic expansion.
  • E. redshiftType
    Indicates the classification of an object's redshift according to how the redshift was determined or what type of redshift it represents.
  • 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_69d8d38ae7e081908a98df1251842402 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e545b8d76881909db1539c7150befb completed April 19, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69e478c98d4c81909d37a0e72c6e7bd0 completed April 19, 2026, 6:40 a.m.
Created at: April 10, 2026, 11:44 a.m.