Triple

T20946548
Position Surface form Disambiguated ID Type / Status
Subject Battle at Rephidim E515857 entity
Predicate hasParticipant P149 FINISHED
Object Hur 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: Hur | Statement: [Battle at Rephidim, hasParticipant, Hur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hur
Context triple: [Battle at Rephidim, hasParticipant, Hur]
  • A. Hur chosen
    Hur is a biblical figure from the Old Testament, traditionally regarded as a leader of Israel and associate of Moses during the Exodus.
  • B. Hor
    Hor is an abbreviated form of the name Horace, often used as a short or familiar version of it.
  • C. Hu
    Hu is a common Chinese surname borne by many notable figures, including former Chinese president Hu Jintao.
  • D. Ho
    Ho are an indigenous Adivasi community of eastern India, primarily inhabiting parts of Jharkhand and Odisha, known for their Austroasiatic Ho language and distinct cultural traditions.
  • E. Ho
    Ho is a town in southeastern Ghana that serves as the capital of the Volta Region and an important administrative and commercial center.
  • 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_69e0b4fcd678819087a304291f14330a completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fad97aa48190b4be692e3afce8c9 completed April 21, 2026, 4:19 a.m.
Created at: April 16, 2026, 12:56 p.m.