Triple
T38292866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safavid garrison of Isfahan |
E1022407
|
entity |
| Predicate | capitalOfWhichDynasty |
P180697
|
FINISHED |
| Object | Safavid dynasty |
—
|
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: Safavid dynasty | Statement: [Safavid garrison of Isfahan, capitalOfWhichDynasty, Safavid dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalOfWhichDynasty Context triple: [Safavid garrison of Isfahan, capitalOfWhichDynasty, Safavid dynasty]
-
A.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
B.
importantDynastyCenterFor
Indicates that a location served as a significant political, cultural, or administrative center for a particular dynasty.
-
C.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
D.
hasCapitalInDynasty
chosen
Indicates that a particular city or location served as the capital during a specified dynasty or historical ruling period.
-
E.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
- F. None of above.
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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:30 p.m.