Triple

T7817435
Position Surface form Disambiguated ID Type / Status
Subject Smithsonian Astrophysical Observatory Telescope Data Center E181045 entity
Predicate dataFrom P68023 FINISHED
Object ground-based telescopes 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: ground-based telescopes | Statement: [Smithsonian Astrophysical Observatory Telescope Data Center, dataFrom, ground-based telescopes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataFrom
Context triple: [Smithsonian Astrophysical Observatory Telescope Data Center, dataFrom, ground-based telescopes]
  • A. dataFile
    Indicates a relationship where one entity serves as or is associated with a specific data file used, stored, or referenced by another entity.
  • B. dataAcquisition chosen
    Indicates the process by which one entity obtains, collects, or retrieves data from another source or system.
  • C. dataPortal
    Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
  • D. dataReturned
    Indicates that some data has been sent back or provided as a result of a request, query, or operation.
  • E. dataInterface
    Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
  • 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_69ca828153f48190bdb27ac46f8e0745 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69caf96ea6d881908eff5f750e0f6700 completed March 30, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69cae91687788190af9cb7aaa996d291 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:40 p.m.