Triple
T20802551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMNP |
E512074
|
entity |
| Predicate | regulatesVendors |
P33535
|
FINISHED |
| Object | authorized farmers |
—
|
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: authorized farmers | Statement: [FMNP, regulatesVendors, authorized farmers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesVendors Context triple: [FMNP, regulatesVendors, authorized farmers]
-
A.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
-
B.
regulatesProduct
Indicates that one entity exercises control or governance over the production, distribution, or characteristics of a product belonging to or associated with another entity.
-
C.
regulatesIn
chosen
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
-
D.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
E.
regulatesOrServes
Indicates that one entity controls, governs, or provides a service or function for 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b207c48190a9ca5895bdf85245 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:39 p.m.