Triple
T6805923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javad Uyezd |
E156305
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Javad |
E619549
|
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: Javad | Statement: [Javad Uyezd, namedAfter, Javad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Javad Context triple: [Javad Uyezd, namedAfter, Javad]
-
A.
Javad
chosen
Javad was a historical town in the South Caucasus region that served as the administrative center of the Javad Uyezd in the Russian Empire.
-
B.
Reza
Reza is the given name of Reza Shah Pahlavi, the founder of the Pahlavi dynasty and modernizing monarch of Iran in the early 20th century.
-
C.
Ramin
Ramin is a masculine given name of Persian origin, commonly used in Iran and among Persian-speaking communities.
-
D.
Hamed
Hamed is a masculine given name commonly used in Arabic-speaking and Muslim-majority cultures.
-
E.
Jamshid
Jamshid is a legendary king in Persian mythology, renowned for his long, prosperous reign and his central role in ancient Iranian cultural and epic traditions.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d3082dcc8190a84bc056236cc52e |
completed | March 27, 2026, 6:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c72f9926ec8190bff8d01e3ab0d0da |
completed | March 28, 2026, 1:32 a.m. |
Created at: March 27, 2026, 2:16 p.m.