Triple

T34071477
Position Surface form Disambiguated ID Type / Status
Subject NGC 7174 E873779 entity
Predicate hasPeculiarVelocity P195467 FINISHED
Object true 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: true | Statement: [NGC 7174, hasPeculiarVelocity, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPeculiarVelocity
Context triple: [NGC 7174, hasPeculiarVelocity, true]
  • A. hasRadialVelocityMeasurement
    Indicates that a radial velocity value has been measured for an entity, typically quantifying its motion along the line of sight relative to an observer.
  • B. hasRadialVelocityRelativeToLocalGroup
    Indicates that an object has a measured radial (line-of-sight) velocity with respect to the reference frame of the Local Group of galaxies.
  • C. hasRadialVelocitySignature
    Indicates that an object exhibits a measurable radial velocity pattern characteristic of a specific physical process or source.
  • D. hasRadialVelocity_km_per_s
    Indicates that one entity has a measured radial velocity, expressed in kilometers per second, relative to another reference frame or object.
  • E. hasTypicalVelocity
    Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fdd2be648c8190b60b3d1caeb44364 completed May 8, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69fdd14a5c708190a6f95ec61f4fc28f completed May 8, 2026, 12:04 p.m.
PDg Predicate description generation batch_69fdd2bda90881909aa229194d014ba7 completed May 8, 2026, 12:10 p.m.
Created at: May 1, 2026, 1:52 a.m.