Triple

T17556911
Position Surface form Disambiguated ID Type / Status
Subject Re-Harakhty E427612 entity
Predicate combinesDeity P32453 FINISHED
Object Ra NE NERFINISHED

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: Ra | Statement: [Re-Harakhty, combinesDeity, Ra]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ra
Context triple: [Re-Harakhty, combinesDeity, Ra]
  • A. Ra chosen
    Ra is the ancient Egyptian sun god, revered as a supreme creator deity and central figure in Pharaonic religion and mythology.
  • B. RA
    RA is the vehicle registration code used on license plates for the German town of Kuppenheim in the state of Baden-Württemberg.
  • C. RA
    RA is the commonly used abbreviation for the Royal Regiment of Artillery, a principal artillery branch of the British Army.
  • D. RA
    RA is the commonly used abbreviation for Rugby Australia, the governing body for rugby union in Australia.
  • E. RA
    RA is the abbreviated name commonly used for the Radiocommunications Agency, the UK body formerly responsible for managing the radio spectrum and regulating radio communications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d889df6dc081908f67dbadc03c07ee completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4562357b48190bde6f49df0c983c2 completed April 19, 2026, 4:12 a.m.
Created at: April 10, 2026, 5:50 a.m.