Triple
T19969174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apna Dal |
E480023
|
entity |
| Predicate | baseSupportFrom |
P60372
|
FINISHED |
| Object | rural OBC communities |
—
|
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: rural OBC communities | Statement: [Apna Dal, baseSupportFrom, rural OBC communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseSupportFrom Context triple: [Apna Dal, baseSupportFrom, rural OBC communities]
-
A.
mainSupportBase
Indicates that one entity serves as the primary structural or functional support base for another entity.
-
B.
baseFeature
Indicates that one entity serves as the fundamental or primary feature upon which another entity is built or defined.
-
C.
hasSupportBaseIn
chosen
Indicates that one entity maintains an operational or organizational base of support located in another entity.
-
D.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
E.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc7c2fc81909b89c549a5f99e4c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.