Triple

T34185598
Position Surface form Disambiguated ID Type / Status
Subject NGC 7314 E876948 entity
Predicate hasAGNVariabilityTimescale P178498 FINISHED
Object hours to days 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: hours to days | Statement: [NGC 7314, hasAGNVariabilityTimescale, hours to days]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAGNVariabilityTimescale
Context triple: [NGC 7314, hasAGNVariabilityTimescale, hours to days]
  • A. hasVariability
    Indicates that an entity exhibits variation or fluctuation in its state, value, or characteristics over time or across instances.
  • B. hasCauseOfVariability
    Indicates a relationship where one factor or condition is identified as the source or driver of variation observed in another.
  • C. hasSpectralVariability
    Indicates that an entity exhibits changes or fluctuations in its spectral properties over time or under different conditions.
  • D. hasVariabilityType
    Indicates that an entity is associated with a specific kind or category of variability (e.g., how or in what way it varies).
  • E. variabilityRecognizedIn
    Indicates that variability or variation in one entity is acknowledged, identified, or detected within the context of another entity.
  • 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_69f349ae640c8190b9cd220b5368d8b6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f710aaff588190adc6cc5b7d5424cc completed May 3, 2026, 9:08 a.m.
PD Predicate disambiguation batch_69f70f3c5bfc81908585f52e196dafe5 completed May 3, 2026, 9:02 a.m.
PDg Predicate description generation batch_69f70fddd43c819088dee5a448c72cbe completed May 3, 2026, 9:05 a.m.
Created at: May 1, 2026, 1:55 a.m.