Triple
T15475335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace of Ardashir |
E376768
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Firuzabad |
E587455
|
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: Firuzabad | Statement: [Palace of Ardashir, locatedNear, Firuzabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Firuzabad Context triple: [Palace of Ardashir, locatedNear, Firuzabad]
-
A.
Firuzabad
chosen
Firuzabad is a historic city in Iran renowned for its Sassanian-era archaeological sites and distinctive circular urban plan.
-
B.
Nurabad
Nurabad is a city in western Iran that serves as a local urban center within Lorestan Province.
-
C.
Ardestan
Ardestan is an ancient city in central Iran known for its historic architecture, including notable mosques and traditional urban fabric.
-
D.
Piranshahr
Piranshahr is a predominantly Kurdish city in northwestern Iran known for its mountainous surroundings and role as a regional commercial center.
-
E.
Azarshahr
Azarshahr is a city in northwestern Iran known for its location within East Azerbaijan Province and its role as a local administrative and economic center.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6e859481909c3d08343b7ad27c |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff78dab488190a89b9eb4f648b36c |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 3:34 a.m.