Triple
T20795003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EQIP |
E511887
|
entity |
| Predicate | administersThrough |
P86
|
FINISHED |
| Object | state NRCS offices |
—
|
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: state NRCS offices | Statement: [EQIP, administersThrough, state NRCS offices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administersThrough Context triple: [EQIP, administersThrough, state NRCS offices]
-
A.
administersFrom
Indicates that an action, service, or process is carried out or managed starting from a particular source, location, or authority.
-
B.
administeredAs
Indicates that one entity is given or applied to another entity as a treatment, dose, or intervention.
-
C.
administeredFor
Indicates that something (typically a treatment, medication, or intervention) is given or applied to an entity for a specific purpose, condition, or intended effect.
-
D.
administeredBy
chosen
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
E.
coAdministersWith
Indicates that one entity is administered together with another entity, typically at the same time or as part of the same treatment or process.
- 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.