Triple
T33643816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soil Health Card Scheme |
E861901
|
entity |
| Predicate | cardHolder |
P177461
|
FINISHED |
| Object | individual farmer |
—
|
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: individual farmer | Statement: [Soil Health Card Scheme, cardHolder, individual farmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardHolder Context triple: [Soil Health Card Scheme, cardHolder, individual farmer]
-
A.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
B.
cardSegment
Indicates a relationship where a card is divided into or associated with a specific segment or portion of itself.
-
C.
cardFormat
Indicates the specific layout or structural style in which a card or card-like item is presented or encoded.
-
D.
cardholderSegment
Indicates the classification or grouping assigned to a cardholder based on shared characteristics, behaviors, or status.
-
E.
cardRequiredFor
Indicates that a specific card must be presented or possessed in order to access, use, or complete the related item, service, or action.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:42 a.m.