Triple

T37289808
Position Surface form Disambiguated ID Type / Status
Subject Gurjara E925633 entity
Predicate linkedDynasty P7426 FINISHED
Object Paramaras
The Paramaras were a prominent medieval Indian Rajput dynasty that ruled the Malwa region and surrounding areas, known especially for their patronage of art, literature, and temple architecture.
E2221051 NE 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: Paramaras | Statement: [Gurjara, linkedDynasty, Paramaras]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Paramaras
Triple: [Gurjara, linkedDynasty, Paramaras]
Generated description
The Paramaras were a prominent medieval Indian Rajput dynasty that ruled the Malwa region and surrounding areas, known especially for their patronage of art, literature, and temple architecture.

Provenance (5 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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5ae61d608190b42a7b8314f4a546 completed May 6, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40514203e08190a7b067d8785076d7 completed June 27, 2026, 10:40 p.m.
NEDg Description generation batch_6a4051f3e8d08190b2e0db9d03b3a57e completed June 27, 2026, 10:43 p.m.
NED2 Entity disambiguation (via description) batch_6a4052c3ada481908d4ffbfaad34c24b completed June 27, 2026, 10:46 p.m.
Created at: May 3, 2026, 4:16 p.m.