Triple
T22443627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifth Five-Year Plan of India |
E554814
|
entity |
| Predicate | emphasizedSector |
P83753
|
FINISHED |
| Object | agriculture |
—
|
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: agriculture | Statement: [Fifth Five-Year Plan of India, emphasizedSector, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizedSector Context triple: [Fifth Five-Year Plan of India, emphasizedSector, agriculture]
-
A.
sectorHighlighted
Indicates that a particular sector or segment within a larger structure (such as a chart, map, or system) is visually or logically emphasized or selected.
-
B.
dominatedSector
Indicates that one entity exercises prevailing control or influence over a particular sector relative to others.
-
C.
hasSectoralPriority
Indicates that something is designated as having priority or special importance within a particular sector or industry.
-
D.
emphasizesPolicyArea
chosen
Indicates that one entity gives particular importance or priority to a specific policy area in its actions, statements, or focus.
-
E.
coveredSector
Indicates that one entity provides coverage, service, or operational responsibility for a particular sector or area.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae40f9081908674015beb33f74e |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.