Triple
T32133724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalit Khas |
E820715
|
entity |
| Predicate | barriers |
P52690
|
FINISHED |
| Object | barriers to social mobility |
—
|
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: barriers to social mobility | Statement: [Dalit Khas, barriers, barriers to social mobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barriers Context triple: [Dalit Khas, barriers, barriers to social mobility]
-
A.
isBarrierTo
Indicates that one entity obstructs, prevents, or significantly hinders another entity from occurring, progressing, or being accessed.
-
B.
barrierAddressed
Indicates that an identified obstacle, hindrance, or constraint affecting an entity or process has been actively dealt with, mitigated, or removed.
-
C.
obstacles
chosen
Indicates that one entity presents barriers, hindrances, or impediments that block or restrict another entity’s progress, action, or interaction.
-
D.
facedBarrier
Indicates that an entity encountered an obstacle, hindrance, or restriction that impeded its progress or actions.
-
E.
typicalBarrierType
Indicates the usual or characteristic type of barrier associated with or used in a given context or situation.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9753dc88190ba840384d5936e69 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.