Triple

T4911789
Position Surface form Disambiguated ID Type / Status
Subject Ophiuchus E110248 entity
Predicate hasIAUBoundariesDefinedIn P36415 FINISHED
Object 1930 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: 1930 | Statement: [Ophiuchus, hasIAUBoundariesDefinedIn, 1930]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIAUBoundariesDefinedIn
Context triple: [Ophiuchus, hasIAUBoundariesDefinedIn, 1930]
  • A. hasIAUBoundariesDefinedBy chosen
    Indicates that an entity’s boundaries are defined or delimited according to standards or specifications established by the International Astronomical Union (IAU).
  • B. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • C. hasBoundarySystem
    Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
  • D. hasUncertainBoundary
    Indicates that the boundary or extent of something is not clearly defined, fixed, or precisely known.
  • E. isLegalBoundary
    Indicates that something serves as an officially recognized dividing line that defines the limits of a legal jurisdiction, property, or authority.
  • 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_69bd44132b94819088522d92beaadc78 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e9c32148190a940a3733ecd1898 completed March 20, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69bd6c325e188190823836d79934e9bc completed March 20, 2026, 3:48 p.m.
Created at: March 20, 2026, 1:29 p.m.