Triple
T20691912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CROP Education Working Group |
E508572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | education coordination body |
C15085
|
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 coordination body Context triple: [CROP Education Working Group, instanceOf, education coordination body]
-
A.
education policy body
An education policy body is an organization or governing entity responsible for developing, overseeing, and evaluating policies and regulations that shape the structure, standards, and operation of an education system.
-
B.
education regulatory authority
An education regulatory authority is a governing body responsible for setting, monitoring, and enforcing standards, policies, and regulations to ensure the quality, equity, and compliance of educational institutions and systems.
-
C.
national education agency
A national education agency is a government body responsible for developing, coordinating, and overseeing a country’s education policies, standards, and programs across all levels of schooling.
-
D.
education association
chosen
An education association is an organized group that supports, advocates for, and advances the interests, standards, and professional development of individuals and institutions involved in education.
-
E.
education consulting organization
An education consulting organization is a professional service entity that advises students, families, schools, or institutions on academic planning, admissions strategies, program development, and educational improvement.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:09 p.m.