Triple

T3631159
Position Surface form Disambiguated ID Type / Status
Subject Kepler space telescope E76957 entity
Predicate dataReleasePolicy P37827 FINISHED
Object public archive 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: public archive | Statement: [Kepler space telescope, dataReleasePolicy, public archive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataReleasePolicy
Context triple: [Kepler space telescope, dataReleasePolicy, public archive]
  • A. dataPolicy
    Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
  • B. dataPublication chosen
    Indicates that some data has been made publicly available or formally released, typically through a defined dissemination or publishing process.
  • C. openAccessPolicy
    Indicates that an entity has a policy allowing unrestricted or minimally restricted public access to its resources, content, or services.
  • D. collectionPolicy
    Indicates the rules or guidelines that govern how items are gathered, selected, and managed within a collection.
  • E. governingPolicy
    Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions 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_69ad85dc03948190b35b7189e4175bcc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc30136e88190922bb542971b5239 completed March 8, 2026, 6:42 p.m.
PD Predicate disambiguation batch_69adb8410a5881909c94818d7060b2b0 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:23 p.m.