Triple
T28563351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucknow school of Urdu poetry |
E722606
|
entity |
| Predicate | culturalSetting |
P97639
|
FINISHED |
| Object | Nawabi Lucknow |
—
|
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: Nawabi Lucknow | Statement: [Lucknow school of Urdu poetry, culturalSetting, Nawabi Lucknow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalSetting Context triple: [Lucknow school of Urdu poetry, culturalSetting, Nawabi Lucknow]
-
A.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
B.
basedInCulture
chosen
Indicates that an entity is situated within, originates from, or is fundamentally associated with a particular culture.
-
C.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
D.
centralToCultureOf
Indicates that something is a core, defining, and influential element within the culture of a particular group or society.
-
E.
culturalLayer
Indicates the relationship in which something belongs to, originates from, or is associated with a particular cultural stratum, tradition, or level within a culture.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 4:06 a.m.