Triple

T19730088
Position Surface form Disambiguated ID Type / Status
Subject NGC 5236 E473826 entity
Predicate hasNuclearStarburst P57295 FINISHED
Object yes 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: yes | Statement: [NGC 5236, hasNuclearStarburst, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNuclearStarburst
Context triple: [NGC 5236, hasNuclearStarburst, yes]
  • A. containsProminentStarburstGalaxy chosen
    Indicates that the subject region or object includes at least one galaxy characterized by a strong, unusually high rate of star formation (a prominent starburst galaxy).
  • B. hasStarFormationMode
    Indicates the specific manner or process by which star formation occurs in a given astronomical system or region.
  • C. hasCentralStarType
    Indicates that one entity (typically a planetary system) is associated with or characterized by a central star of a specified stellar type.
  • D. notableStarburstGalaxy
    Indicates that the subject is a starburst galaxy recognized as notable or significant in some context.
  • E. hasActiveGalacticNucleus
    Indicates that a galaxy contains an active galactic nucleus, meaning its central region is currently emitting significant energy due to accretion onto a supermassive black hole.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649fbeaf081909e9356229eaf84dd completed April 20, 2026, 3:45 p.m.
PD Predicate disambiguation batch_69e5304a7aac8190ac13f75f0c008e45 completed April 19, 2026, 7:43 p.m.
Created at: April 10, 2026, 1:47 p.m.