Triple
T16782555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persepolis archaeological site |
E407890
|
entity |
| Predicate | originalName |
P65
|
FINISHED |
| Object | Parsa |
E134143
|
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: Parsa | Statement: [Persepolis archaeological site, originalName, Parsa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Parsa Context triple: [Persepolis archaeological site, originalName, Parsa]
-
A.
Parsa
chosen
Parsa is the ancient name of the Persian people and their homeland, from which the ethnonym "Persian" is historically derived.
-
B.
Azarbarzin
Azarbarzin is a character from Persian epic tradition, known primarily as the son of the legendary hero Esfandiyar.
-
C.
Moosavi
Moosavi is a nisba (surname) traditionally used by certain Sayyid families, particularly those tracing their lineage to Musa al-Kadhim in Shia Islam.
-
D.
Delaram
Delaram is a town in southwestern Afghanistan that serves as a key transport hub linking major highways, including routes toward Iran and central Afghanistan.
-
E.
Azmeh
Azmeh is a family name most notably associated with Syrian clarinetist and composer Kinan Azmeh.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b217b2108190bbba262a3b324509 |
completed | April 18, 2026, 4:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00ab056dc88190aeb9e135ae955125 |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 10, 2026, 5:22 a.m.