Triple
T11735414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asaf-ud-Daula |
E279012
|
entity |
| Predicate | culturePromoted |
P57225
|
FINISHED |
| Object | Indo-Persian culture |
—
|
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: Indo-Persian culture | Statement: [Asaf-ud-Daula, culturePromoted, Indo-Persian culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturePromoted Context triple: [Asaf-ud-Daula, culturePromoted, Indo-Persian culture]
-
A.
cultureMedium
Indicates the substance or environment used to grow, maintain, or study a biological specimen or culture.
-
B.
culturalHeritagePromoted
chosen
Indicates that efforts or actions are undertaken to support, publicize, or enhance the visibility and appreciation of a particular cultural heritage.
-
C.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
D.
culturePractice
Indicates a relationship where a group or society engages in, maintains, or performs a particular cultural activity, custom, or tradition.
-
E.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4edced48190b7a59dd45921828e |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.