Triple

T6331935
Position Surface form Disambiguated ID Type / Status
Subject Jørgen Brahe E142400 entity
Predicate relative P37 FINISHED
Object Tycho Brahe E22915 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: Tycho Brahe | Statement: [Jørgen Brahe, relative, Tycho Brahe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tycho Brahe
Context triple: [Jørgen Brahe, relative, Tycho Brahe]
  • A. Tycho Brahe chosen
    Tycho Brahe was a Danish nobleman and astronomer whose precise naked-eye observations of the heavens greatly improved astronomical data and paved the way for Kepler’s laws of planetary motion.
  • B. Abraham Brahe
    Abraham Brahe was a Swedish nobleman of the influential Brahe family and the father of statesman and governor-general Per Brahe the Younger.
  • C. Erik Brahe
    Erik Brahe was a Swedish nobleman and statesman from the influential Brahe family, active in the political life of early modern Sweden.
  • D. Jørgen Brahe
    Jørgen Brahe was a Danish nobleman and foster father of the astronomer Tycho Brahe, playing a key role in raising and educating him.
  • E. Brahe
    Brahe is a noble Scandinavian surname most famously associated with the Danish astronomer Tycho Brahe and his influential family.
  • 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_69c008d4d8e88190ad301c05b08722ac completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0651634b08190b54860ba0a70f5c4 completed March 22, 2026, 9:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d50184a081908286d92166fd1c00 completed March 27, 2026, 7:05 p.m.
Created at: March 22, 2026, 4:30 p.m.