Triple

T4618029
Position Surface form Disambiguated ID Type / Status
Subject Local Hot Bubble E100913 entity
Predicate likelyOriginatedFrom P3654 FINISHED
Object supernovae in the Scorpius–Centaurus OB association 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: supernovae in the Scorpius–Centaurus OB association | Statement: [Local Hot Bubble, likelyOriginatedFrom, supernovae in the Scorpius–Centaurus OB association]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: likelyOriginatedFrom
Context triple: [Local Hot Bubble, likelyOriginatedFrom, supernovae in the Scorpius–Centaurus OB association]
  • A. originallyBy
    Indicates that one entity is the original creator, author, or source of another entity.
  • B. hasOriginIn chosen
    Indicates that something begins, arises, or is derived from a specified source, place, or cause.
  • C. ownedFrom
    Indicates that ownership of an entity began or was acquired starting from a specified time or source.
  • D. missionOrigin
    Indicates the place, organization, or context from which a mission is initiated or originates.
  • E. likelyWrittenFrom
    Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular 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_69bd43cf363c819087fd5ab441b4a3f4 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd59e247448190ad92f194cb1127c5 completed March 20, 2026, 2:29 p.m.
PD Predicate disambiguation batch_69bd522fd5c48190ad2bffc0a5bc9061 completed March 20, 2026, 1:57 p.m.
Created at: March 20, 2026, 1:12 p.m.