Triple
T9718596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hejaz Railway |
E235404
|
entity |
| Predicate | connects |
P390
|
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: [Hejaz Railway, connects, Amman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amman Context triple: [Hejaz Railway, connects, 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.
Ma’an
Ma’an is a major city in southern Jordan that serves as an important regional hub and gateway to nearby desert and archaeological sites.
-
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.
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.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3ea61081908a5671fc5be9a738 |
completed | April 1, 2026, 10:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f986f48819090376fb5aafb3da2 |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:20 p.m.