Triple

T10689691
Position Surface form Disambiguated ID Type / Status
Subject Battle of Emesa E251976 entity
Predicate place P373 FINISHED
Object Emesa E302263 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: Emesa | Statement: [Battle of Emesa, place, Emesa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Emesa
Context triple: [Battle of Emesa, place, Emesa]
  • A. Emesa chosen
    Emesa is the ancient name of the Syrian city now known as Homs, historically significant as a religious and trading center in Roman and early Christian times.
  • B. Eliada
    Eliada is a lesser-known biblical figure mentioned in the Old Testament as one of King David’s sons.
  • C. Almeirim
    Almeirim is a Portuguese city in the Ribatejo region, known for its agricultural traditions and its famous sopa da pedra (stone soup).
  • D. Huraymila
    Huraymila is a small town in central Saudi Arabia known for its traditional character and location within the greater Riyadh region.
  • E. Temara
    Temara is a coastal city in northwestern Morocco, situated just south of Rabat and known for its beaches and growing residential and industrial areas.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fd1c0f0081908a6869ee756ec789 completed April 9, 2026, 1:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69d988a59d6c8190a0e170acfb3af6da completed April 10, 2026, 11:32 p.m.
Created at: April 8, 2026, 9:11 p.m.