Triple
T23850230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | شیراز |
E592140
|
entity |
| Predicate | نقش_تاریخی |
P154179
|
FINISHED |
| Object | پایتخت سلسله زندیه |
—
|
LITERAL 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: پایتخت سلسله زندیه | Statement: [شیراز, نقش_تاریخی, پایتخت سلسله زندیه]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: نقش_تاریخی Context triple: [شیراز, نقش_تاریخی, پایتخت سلسله زندیه]
-
A.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
B.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
C.
historicalWork
Indicates that one entity is a work (such as a document, artifact, or creation) that originates from or pertains to a past historical period in relation to another entity.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
politicalHistory
Indicates that there exists a historical political relationship, involvement, or background connecting the entities, such as past offices held, affiliations, or political events linking them.
- F. None of above. chosen
Provenance (4 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c986f7e08190a6d361423946ff05 |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:11 p.m.