Triple
T18520031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas–Fort Worth AMBER Alert program |
E452559
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | child abduction emergency notification system |
C22284
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: child abduction emergency notification system Context triple: [Dallas–Fort Worth AMBER Alert program, instanceOf, child abduction emergency notification system]
-
A.
kidnapping victim
A kidnapping victim is an individual who is unlawfully taken, held, or transported against their will by another person or group, typically for ransom, coercion, or other criminal purposes.
-
B.
kidnapping
Kidnapping is the unlawful taking and carrying away of a person by force, threat, or deception, often with the intent to confine, ransom, exploit, or otherwise control the victim against their will.
-
C.
child protection mechanism
A child protection mechanism is a system of policies, procedures, and tools designed to prevent, detect, and respond to abuse, neglect, or exploitation of children, ensuring their safety and well-being.
-
D.
witness protection program
A witness protection program is a government-run system that safeguards threatened witnesses and their families by providing security, relocation, and new identities in exchange for their cooperation in legal proceedings.
-
E.
public safety system
chosen
A public safety system is an integrated framework of technologies, policies, and coordinated services designed to prevent, detect, respond to, and recover from threats or emergencies affecting the well-being of a community.
- F. None of above.
Provenance (1 batch)
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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.