Triple
T33643796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soil Health Card Scheme |
E861901
|
entity |
| Predicate | timeFramePerCard |
P302
|
FINISHED |
| Object | once in 2 years |
—
|
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: once in 2 years | Statement: [Soil Health Card Scheme, timeFramePerCard, once in 2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFramePerCard Context triple: [Soil Health Card Scheme, timeFramePerCard, once in 2 years]
-
A.
timeFrameSpecified
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
B.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
numberOfTimeSlotsPerFrame
Indicates the total count of discrete time slots that are contained within a single frame in a time-structured system or protocol.
-
D.
frameDuration
Indicates the length of time that a single frame in a sequence (such as video or animation) is displayed before advancing to the next frame.
-
E.
timeframeOfUse
Indicates the period or duration during which something is intended, allowed, or expected to be used.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.