Triple

T4618987
Position Surface form Disambiguated ID Type / Status
Subject the Teapot E100932 entity
Predicate hasMnemonicRole P6239 FINISHED
Object helps observers remember Sagittarius star layout 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: helps observers remember Sagittarius star layout | Statement: [the Teapot, hasMnemonicRole, helps observers remember Sagittarius star layout]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMnemonicRole
Context triple: [the Teapot, hasMnemonicRole, helps observers remember Sagittarius star layout]
  • A. hasBorderRole
    Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
  • B. hasPrimaryFocus
    Indicates that something is the main subject, concern, or area of attention for an entity or activity.
  • C. hasNavigationCharacteristic
    Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
  • D. hasAuxiliaryRole chosen
    Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
  • E. hasRelativeRole
    Indicates that one entity holds a familial or kinship-based role in relation to another 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_69bd59e3e6948190925e2cfad20dcc8c 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.