Triple
T22820486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deh Rawud District |
E565213
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Deh Rawud |
—
|
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: Deh Rawud | Statement: [Deh Rawud District, capital, Deh Rawud]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deh Rawud Context triple: [Deh Rawud District, capital, Deh Rawud]
-
A.
Deh Rawud
chosen
Deh Rawud is a town and district center in Uruzgan Province in central Afghanistan, known for its strategic location in a mountainous, conflict-affected region.
-
B.
Rutba
Rutba is a remote desert town in western Iraq that serves as a key transit point on the highway linking Baghdad with Jordan and Syria.
-
C.
Rudsar
Rudsar is a coastal city in northern Iran known for its lush landscapes, rice paddies, and proximity to the Caspian Sea.
-
D.
Derabish
Derabish is a town and administrative block in the Kendrapara district of the Indian state of Odisha.
-
E.
Yaghma
Yaghma was a Turkic tribal clan that rose to prominence as the ruling dynasty of the Kara-Khanid Khanate in Central Asia.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcffdd88190a5f9c780c71b5053 |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:33 p.m.