Triple
T13915481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afshar (Afsharid-related) lineage |
E334609
|
entity |
| Predicate | roseAfter |
P1691
|
FINISHED |
| Object | decline of the Safavid dynasty |
—
|
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: decline of the Safavid dynasty | Statement: [Afshar (Afsharid-related) lineage, roseAfter, decline of the Safavid dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roseAfter Context triple: [Afshar (Afsharid-related) lineage, roseAfter, decline of the Safavid dynasty]
-
A.
after
chosen
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
B.
releasedAfterSuccessOf
Indicates that one entity was released following, and likely in response to, the successful performance or reception of another entity.
-
C.
roséShare
Indicates a relationship where one entity shares rosé wine with another entity.
-
D.
roseToPowerThrough
Indicates the means, process, or circumstances by which an entity gained authority, control, or a dominant position.
-
E.
roseToProminenceUnder
Indicates that an entity became well-known, influential, or successful during the period of another entity’s leadership, guidance, or dominance.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de27260ae08190be45b4b15898e365 |
completed | April 14, 2026, 11:38 a.m. |
| PD | Predicate disambiguation | batch_69de059e4ba881908554f72e889719fa |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:16 p.m.