Triple
T23046848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajput courts |
E573898
|
entity |
| Predicate | developedTradition |
P64101
|
FINISHED |
| Object | Rajput courtly 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: Rajput courtly culture | Statement: [Rajput courts, developedTradition, Rajput courtly culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedTradition Context triple: [Rajput courts, developedTradition, Rajput courtly culture]
-
A.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
establishedTradition
chosen
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
D.
cultOrTradition
Indicates that one entity is a cult or tradition associated with, practiced by, or characterizing another entity.
-
E.
exploresTradition
Indicates an entity actively investigates, examines, or engages with a tradition to understand or interpret it.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18678e5c48190a96a7b4c9c82f8fe |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:54 p.m.