Triple
T5890233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Instant Criminal Background Check System |
E130969
|
entity |
| Predicate | processingTimeGoal |
P55905
|
FINISHED |
| Object | within minutes |
—
|
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: within minutes | Statement: [National Instant Criminal Background Check System, processingTimeGoal, within minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingTimeGoal Context triple: [National Instant Criminal Background Check System, processingTimeGoal, within minutes]
-
A.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
B.
intendedResponseTime
chosen
Indicates the expected or planned amount of time within which a response should be given or received.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
agingTimeMinimum
Indicates the minimum amount of time that must elapse for something to be considered aged or matured according to a specified standard.
- 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_69c0085628dc8190b334c1b44c067efc |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03fe07b7081909f8577ec3a9a1a8d |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0334bdc308190ad0d7199ab975588 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.