Triple

T11376983
Position Surface form Disambiguated ID Type / Status
Subject Hercules E269493 entity
Predicate hasStar P3335 FINISHED
Object η Herculis E918816 NE 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: η Herculis | Statement: [Hercules, hasStar, η Herculis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: η Herculis
Context triple: [Hercules, hasStar, η Herculis]
  • A. η Herculis chosen
    η Herculis is a bright giant star in the constellation Hercules, visible to the naked eye and used as a reference point near the globular cluster M13.
  • B. α Herculis
    α Herculis is a bright multiple star system in the constellation Hercules, dominated by a luminous red giant visible to the naked eye.
  • C. ζ Herculis
    ζ Herculis is a bright binary star system in the constellation Hercules, visible to the naked eye and composed of two closely orbiting Sun-like stars.
  • D. δ Herculis
    δ Herculis is a bright multiple star system in the constellation Hercules, visible to the naked eye and commonly used as a reference point in the northern sky.
  • E. β Herculis
    β Herculis is a bright binary star system in the constellation Hercules, commonly known by its traditional name Kornephoros.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea8e6d44819095f949581421e98e completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e603d2320c81909ed6946c7b7dfb36 completed April 20, 2026, 10:45 a.m.
Created at: April 8, 2026, 9:33 p.m.