Triple
T6652640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalit |
E150858
|
entity |
| Predicate | positionInCasteSystem |
P72102
|
FINISHED |
| Object | outside traditional Hindu caste hierarchy |
—
|
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: outside traditional Hindu caste hierarchy | Statement: [Dalit, positionInCasteSystem, outside traditional Hindu caste hierarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCasteSystem Context triple: [Dalit, positionInCasteSystem, outside traditional Hindu caste hierarchy]
-
A.
positionInCast
Indicates the specific role or placement an individual holds within the cast of a production, such as their billing order or credited position.
-
B.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
C.
positionWithinCastle
Indicates that one entity is located inside the spatial boundaries of a castle.
-
D.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
E.
positionInLeagueSystem
Indicates the rank or tier an entity holds within an organized league or competitive system.
- F. None of above. chosen
Provenance (4 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.