Triple

T21965752
Position Surface form Disambiguated ID Type / Status
Subject Battle of Aqaba E542451 entity
Predicate location P40 FINISHED
Object Aqaba 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: Aqaba | Statement: [Battle of Aqaba, location, Aqaba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aqaba
Context triple: [Battle of Aqaba, location, Aqaba]
  • A. Aqaba chosen
    Aqaba is Jordan’s only coastal city, a key Red Sea port and popular resort destination known for its beaches, coral reefs, and strategic location near the borders with Israel, Egypt, and Saudi Arabia.
  • B. Salalah
    Salalah is a coastal city in southern Oman known for its monsoon-cooled climate, lush green landscapes, and role as a regional tourism and commercial hub.
  • C. El Arish
    El Arish is a coastal city in northeastern Egypt on the Mediterranean Sea, serving as the capital and main urban center of North Sinai Governorate.
  • D. Mafraq
    Mafraq is a city in northern Jordan that serves as a strategic transport hub and gateway to the Syrian border and surrounding desert regions.
  • E. Port of Aqaba
    The Port of Aqaba is Jordan’s only seaport and a key Red Sea maritime hub for the country’s trade and naval operations.
  • 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_69e0c47fab1081908dc74a6545dbb051 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1245aabf88190a44564e6eaaa94ce completed April 28, 2026, 9:19 p.m.
Created at: April 16, 2026, 8:01 p.m.