Triple
T20794947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Food Security Act conservation provisions |
E511886
|
entity |
| Predicate | targetsResourceConcern |
P64698
|
FINISHED |
| Object | highly erodible land |
—
|
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: highly erodible land | Statement: [Food Security Act conservation provisions, targetsResourceConcern, highly erodible land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsResourceConcern Context triple: [Food Security Act conservation provisions, targetsResourceConcern, highly erodible land]
-
A.
targetConcern
chosen
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
B.
targetResource
Indicates that one entity designates another entity as the specific resource or object toward which an action, request, or operation is directed.
-
C.
concernsEntity
Indicates that something (such as an action, issue, or piece of information) is about or relevant to a particular entity.
-
D.
centralResource
Indicates that one entity functions as the primary or core resource upon which another entity depends or is organized.
-
E.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2abbcc8819091bb0225a0650ab6 |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.