Triple
T14554540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraq-i Ajam |
E341504
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Borujerd |
E921044
|
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: Borujerd | Statement: [Iraq-i Ajam, hasMajorCity, Borujerd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borujerd Context triple: [Iraq-i Ajam, hasMajorCity, Borujerd]
-
A.
Borujerd
chosen
Borujerd is a major city in western Iran known as an important cultural and economic center within Lorestan Province.
-
B.
Bojnurd
Bojnurd is a city in northeastern Iran that serves as the capital of North Khorasan Province.
-
C.
Birjand
Birjand is a city in eastern Iran that serves as the capital of South Khorasan Province and is known for its historical forts and saffron production.
-
D.
Juybar
Juybar is a small city in northern Iran known for its location in the fertile, Caspian coastal region of Mazandaran.
-
E.
Sanandaj
Sanandaj is the capital of Iran’s Kurdistan Province, known for its Kurdish culture, traditional music, and mountainous surroundings in western Iran.
- 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2f00cec8190a7b6482d18b9a216 |
completed | April 14, 2026, 9:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff90815b64819082715292f6088c74 |
completed | May 9, 2026, 7:52 p.m. |
Created at: April 10, 2026, 1:23 a.m.