Triple
T21051153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jawad |
E518584
|
entity |
| Predicate | alternativeTransliteration |
P5923
|
FINISHED |
| Object | Javad |
—
|
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: Javad | Statement: [Jawad, alternativeTransliteration, Javad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Javad Context triple: [Jawad, alternativeTransliteration, 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.
Parviz
Parviz is a masculine given name of Persian origin commonly used in Iran and among Persian-speaking communities.
-
D.
Fariborz
Fariborz is a Persian given name commonly used for men, particularly in Iran and among the Iranian diaspora.
-
E.
Rūzbeh
Rūzbeh was the original Persian name of Ibn al-Muqaffaʿ, the influential 8th-century translator and prose stylist who helped shape early Arabic literature.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7bd96c81909cb46419ad4e1222 |
completed | April 21, 2026, 4:30 a.m. |
Created at: April 16, 2026, 2:35 p.m.