Triple

T21027199
Position Surface form Disambiguated ID Type / Status
Subject Tully-Fisher relation distances E517969 entity
Predicate usesObservable P20811 FINISHED
Object galaxy rotational line width 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: galaxy rotational line width | Statement: [Tully-Fisher relation distances, usesObservable, galaxy rotational line width]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesObservable
Context triple: [Tully-Fisher relation distances, usesObservable, galaxy rotational line width]
  • A. isObservedUsing
    Indicates that an entity is observed or monitored by means of a specified instrument, method, or medium.
  • B. observedWith
    Indicates that two or more entities are seen, detected, or recorded together in the same context, event, or observation.
  • C. observableWith chosen
    Indicates that one entity can be detected, measured, or perceived through the use of another specified entity or method.
  • D. observesIn
    Indicates that one entity observes, monitors, or takes note of another entity within a specific context, environment, or scope.
  • E. observedFor
    Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis 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_69e0b503275c8190afd9a163f997c709 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc7d93908190a2c29a4051fb5acc completed April 21, 2026, 4:26 a.m.
PD Predicate disambiguation batch_69e5dbf274ac81909bbf245627dc8fdc completed April 20, 2026, 7:55 a.m.
Created at: April 16, 2026, 1:55 p.m.