Triple

T18552139
Position Surface form Disambiguated ID Type / Status
Subject Cassiopeia E453402 entity
Predicate meteorShowerRadiant P132128 FINISHED
Object Perseids vicinity 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: Perseids vicinity | Statement: [Cassiopeia, meteorShowerRadiant, Perseids vicinity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: meteorShowerRadiant
Context triple: [Cassiopeia, meteorShowerRadiant, Perseids vicinity]
  • A. meteorShower
    Indicates an event where numerous meteors enter a planet’s atmosphere in a short period, typically appearing as a concentrated display of shooting stars.
  • B. meteorShowers
    Indicates that one or more meteor showers occur, are present, or are being observed in relation to the specified entities.
  • C. relatedMeteorShowers
    Indicates that two or more meteor showers are connected by a meaningful relationship, such as sharing a common origin, time period, or observational characteristics.
  • D. meteoroidSource
    Indicates that one entity is the origin or source from which the meteoroid represented by the other entity comes.
  • E. meteorBrightness
    Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
  • 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e538019a74819099dbd255fb21fa95 completed April 19, 2026, 8:16 p.m.
PD Predicate disambiguation batch_69e469e274a48190a570b25cfef4d890 completed April 19, 2026, 5:36 a.m.
PDg Predicate description generation batch_69e46d2b93bc8190a6070018d7046547 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 11:38 a.m.