Triple

T27743648
Position Surface form Disambiguated ID Type / Status
Subject Halley’s Comet E701919 entity
Predicate hasDustProduction P101037 FINISHED
Object significant dust jets observed near perihelion 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: significant dust jets observed near perihelion | Statement: [Halley’s Comet, hasDustProduction, significant dust jets observed near perihelion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDustProduction
Context triple: [Halley’s Comet, hasDustProduction, significant dust jets observed near perihelion]
  • A. hasDust
    Indicates that one entity possesses, contains, or is covered with dust.
  • B. hasDustStructure
    Indicates that one entity possesses or exhibits a particular dust-related structure or configuration.
  • C. producesAerosol chosen
    Indicates that one entity generates or emits an aerosol (a suspension of fine solid particles or liquid droplets in air) as a result of its action or process.
  • D. hasProductionFacilitiesIn
    Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
  • E. dustDynamics
    Indicates how dust particles move, interact, and evolve over time within a physical or astrophysical environment.
  • 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_69ef6a53c7388190899baa6daf42301c completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69f63894e5848190aec428392562ab06 completed May 2, 2026, 5:47 p.m.
PD Predicate disambiguation batch_69f6370c8c7c8190a02ea82847bb6e76 completed May 2, 2026, 5:40 p.m.
Created at: April 27, 2026, 4:13 p.m.