Triple

T12316654
Position Surface form Disambiguated ID Type / Status
Subject Jabal al-Druze E293616 entity
Predicate bordersRegion P224 FINISHED
Object Hauran E571616 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: Hauran | Statement: [Jabal al-Druze, bordersRegion, Hauran]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hauran
Context triple: [Jabal al-Druze, bordersRegion, Hauran]
  • A. Hauran chosen
    Hauran is a historical region in southwestern Syria and northwestern Jordan, known for its fertile volcanic plains and ancient settlements.
  • B. Harauti
    Harauti is an Indo-Aryan dialect of the Rajasthani language spoken primarily in the Hadoti region of Rajasthan, India.
  • C. Horki
    Horki is a town in eastern Belarus known for its agricultural academy and regional administrative significance.
  • D. Harestua
    Harestua is a village in Viken county, Norway, known for its residential community and proximity to the Harestua Solar Observatory.
  • E. Roura
    Roura is a commune in French Guiana known for its rainforest landscapes and proximity to the Kaw-Roura Marshland Nature Reserve.
  • 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_69d6ab6a2b50819082f6aedd32ed608a completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d93f05186481909c024a933b4f6c60 completed April 10, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69f634688f548190b3c9013591da939b completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:53 p.m.