Triple
T9186441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Riyadh |
E220470
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Najd |
E44274
|
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: Najd | Statement: [Battle of Riyadh, region, Najd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Najd Context triple: [Battle of Riyadh, region, Najd]
-
A.
Najd
chosen
Najd is the central plateau region of Saudi Arabia, historically known as a heartland of Arab tribal culture and the birthplace of the modern Saudi state.
-
B.
Zau
Zau is an ancient city, historically known as Sais, that served as an important religious and political center in Egypt’s Nile Delta.
-
C.
Tayshet
Tayshet is a town in Irkutsk Oblast, Russia, known as a major railway junction in Siberia.
-
D.
Bayanhot
Bayanhot is the administrative center and main urban settlement of Alxa League in western Inner Mongolia, China.
-
E.
Nadym
Nadym is a town in the Yamalo-Nenets Autonomous Okrug of Russia, known as a regional center for the natural gas industry and served by its own airport.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc31a52508190a83ccd76f3aa039b |
completed | April 1, 2026, 7:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d065d336a081909c092230e4a46f4e |
completed | April 4, 2026, 1:13 a.m. |
Created at: March 30, 2026, 7:24 p.m.