Triple

T4361003
Position Surface form Disambiguated ID Type / Status
Subject Jordanian Parliament E98659 entity
Predicate meetsIn P40 FINISHED
Object Amman E15311 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: Amman | Statement: [Jordanian Parliament, meetsIn, Amman]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amman
Context triple: [Jordanian Parliament, meetsIn, Amman]
  • A. Amman chosen
    Amman is the capital and largest city of Jordan, serving as a major political, economic, and cultural center in the Arab world.
  • B. Irbid
    Irbid is a large city in northern Jordan known as an important economic, educational, and cultural center.
  • C. 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.
  • D. Aqaba
    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.
  • E. Aleppo
    Aleppo is an ancient and historically significant city in northern Syria, renowned for its rich cultural heritage, medieval architecture, and role as a major trading hub along the Silk Road.
  • 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_69b3454c772081908e20173e379e8ebe completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b351e47d388190b31500189577cd75 completed March 12, 2026, 11:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5dbad2f908190b5ee53bc7f2294c9 completed March 14, 2026, 10:05 p.m.
Created at: March 12, 2026, 11:16 p.m.