Triple
T5422482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Academy of the Bran |
E121284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory body for language |
C3356
|
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: regulatory body for language Context triple: [Academy of the Bran, instanceOf, regulatory body for language]
-
A.
language regulator
chosen
A language regulator is an entity or institution that oversees, standardizes, and guides the usage, evolution, and norms of a language within a community or region.
-
B.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
-
C.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
financial regulatory coordination body
A financial regulatory coordination body is an organization that facilitates collaboration, information-sharing, and policy alignment among multiple financial regulators to promote consistent oversight, reduce systemic risk, and address cross-border or cross-sector regulatory issues.
-
E.
language revitalization organization
A language revitalization organization is a group dedicated to preserving, strengthening, and promoting the use of endangered or marginalized languages through education, community programs, documentation, and advocacy.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:06 p.m.