Triple
T3848522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pandey |
E85231
|
entity |
| Predicate | socialStratum |
P8198
|
FINISHED |
| Object | upper-caste communities in traditional varna system |
—
|
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: upper-caste communities in traditional varna system | Statement: [Pandey, socialStratum, upper-caste communities in traditional varna system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStratum Context triple: [Pandey, socialStratum, upper-caste communities in traditional varna system]
-
A.
socialType
Indicates the category or nature of a social relationship or interaction that exists between entities.
-
B.
socialComposition
chosen
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
C.
socialStance
Indicates the attitude, position, or orientation one entity holds toward another in a social context.
-
D.
socialSphere
Indicates the social environment or network within which an entity regularly interacts or maintains relationships.
-
E.
socialBase
Indicates a foundational social relationship or structure that underlies or supports interactions between entities.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeebcc8a0481909c35161336bdfbf9 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.