Triple

T5380227
Position Surface form Disambiguated ID Type / Status
Subject Sagittarius Arm E113062 entity
Predicate galacticStructureRole P22653 FINISHED
Object connects inner and outer Milky Way regions 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: connects inner and outer Milky Way regions | Statement: [Sagittarius Arm, galacticStructureRole, connects inner and outer Milky Way regions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: galacticStructureRole
Context triple: [Sagittarius Arm, galacticStructureRole, connects inner and outer Milky Way regions]
  • A. galacticComponent
    Indicates that one entity is a structural part or subregion of a galaxy, such as a disk, bulge, halo, or similar galactic subdivision.
  • B. roleInGalaxy chosen
    Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
  • C. MilkyWaySubgroup
    Indicates that one astronomical object is a member of the Milky Way subgroup within the Local Group of galaxies.
  • D. roleInConstellation
    Indicates the specific function or position an entity holds within a particular constellation.
  • E. isInGalaxy
    Indicates that one astronomical object is located within or belongs to a particular galaxy.
  • 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_69bd4436a1988190af18dcff7fd306b4 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd88801b188190b9ac35ed89167fa3 completed March 20, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69bd846172788190969f24bc7503c05e completed March 20, 2026, 5:31 p.m.
Created at: March 20, 2026, 2:03 p.m.