Triple

T21557369
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Moab E531928 entity
Predicate majorCity P316 FINISHED
Object Nebo 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: Nebo | Statement: [Kingdom of Moab, majorCity, Nebo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nebo
Context triple: [Kingdom of Moab, majorCity, Nebo]
  • A. Nebo chosen
    Nebo is an ancient city located in the biblical region of Moab, often associated with nearby Mount Nebo east of the Jordan River.
  • B. Avar Koysu
    Avar Koysu is a mountain river in Dagestan, Russia, that forms one of the main headwaters of the Sulak River as it flows through the Caucasus.
  • C. Vishvayu
    Vishvayu is a lesser-known figure in Hindu mythology, identified in some genealogies as a son of the lunar dynasty king Pururavas.
  • D. Urana
    Urana is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural surroundings and historic country character.
  • E. Danu
    Danu are an ethnic group in Myanmar, primarily known for their agricultural communities and cultural presence in the Shan State region.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eed2e04b048190ac3a9913094b4625 completed April 27, 2026, 3:07 a.m.
Created at: April 16, 2026, 6:29 p.m.