Triple

T3615003
Position Surface form Disambiguated ID Type / Status
Subject Sagan E76578 entity
Predicate germanName P6492 FINISHED
Object Sagan E359976 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: Sagan | Statement: [Sagan, germanName, Sagan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sagan
Context triple: [Sagan, germanName, Sagan]
  • A. Sagan
    Sagan is a town in present-day Żagań, Poland, historically known as a center where the astronomer Johannes Kepler conducted part of his scientific work.
  • B. Sagan chosen
    Sagan is a surname most famously associated with astronomer and science communicator Carl Sagan and his family.
  • C. Niven
    Niven is a Scottish-origin surname most famously associated with the English actor David Niven.
  • D. Bardeen
    Bardeen is a surname most notably associated with John Bardeen, the American physicist who won the Nobel Prize in Physics twice for his work on the transistor and superconductivity.
  • E. Sandage
    Sandage is a surname most notably associated with Allan R. Sandage, a prominent American astronomer known for his work on the expansion rate and age of the universe.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc27b5e008190a72a8dab7d736e64 completed March 8, 2026, 6:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b433184a4081908598f4084e959c2e completed March 13, 2026, 3:54 p.m.
Created at: March 8, 2026, 3:23 p.m.