Triple
T23513915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Educational Rights and Privacy Act |
E572504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | education privacy law |
C5892
|
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: education privacy law Context triple: [Family Educational Rights and Privacy Act, instanceOf, education privacy law]
-
A.
privacy law
Privacy law is the body of legal rules and principles that governs the collection, use, storage, and disclosure of personal information to protect individuals’ privacy rights.
-
B.
education law
chosen
Education law is the body of statutes, regulations, and case law that governs how educational institutions operate, the rights and responsibilities of students, parents, teachers, and administrators, and the allocation and oversight of educational resources.
-
C.
legal education authority
A legal education authority is an organization or body responsible for setting standards, regulating, and overseeing the quality, accreditation, and delivery of legal education and professional training within a jurisdiction.
-
D.
intelligence law
Intelligence law is the body of legal rules, principles, and oversight mechanisms that govern the collection, analysis, sharing, and use of intelligence by state and related actors to protect national security while safeguarding rights and liberties.
-
E.
research law
Research law is the systematic study and application of legal principles, regulations, and ethical standards that govern the conduct, funding, dissemination, and impact of scientific and scholarly research.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 6:08 p.m.