Triple
T25614854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intentional Adulteration (food defense) rule |
E642129
|
entity |
| Predicate | CFRLocation |
P15985
|
FINISHED |
| Object | 21 CFR Part 121 |
—
|
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: 21 CFR Part 121 | Statement: [Intentional Adulteration (food defense) rule, CFRLocation, 21 CFR Part 121]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CFRLocation Context triple: [Intentional Adulteration (food defense) rule, CFRLocation, 21 CFR Part 121]
-
A.
coreLocation
Indicates that one entity serves as the central or primary location associated with another entity.
-
B.
refersToLocation
chosen
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
C.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
D.
definesLocation
Indicates that one entity specifies or establishes the spatial or geographic position of another entity.
-
E.
textLocation
Indicates the spatial or positional relationship of a piece of text within a larger document, page, or layout.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5f9e6ff5481909a8543e6df777725 |
completed | May 2, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:59 p.m.