Triple
T9312430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RALOs |
E224036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Regional At-Large Organization |
C27012
|
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: Regional At-Large Organization Context triple: [RALOs, instanceOf, Regional At-Large Organization]
-
A.
Regional Internet Registry
A Regional Internet Registry is an organization responsible for allocating, registering, and managing Internet number resources (such as IP addresses and AS numbers) within a specific geographic region.
-
B.
NJCAA region
An NJCAA region is a geographically defined grouping of two-year colleges organized under the National Junior College Athletic Association to structure intercollegiate athletic competition and administration.
-
C.
regional chapter network
A regional chapter network is a coordinated system of local chapters within a defined geographic area that collaborate under a shared mission, governance structure, and resource framework to advance common goals.
-
D.
regional academic organization
A regional academic organization is a collaborative association of educational and research institutions within a specific geographic area that coordinates scholarly activities, promotes academic standards, and supports shared resources and initiatives.
-
E.
regional collaborative network
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
- F. None of above. chosen
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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:37 p.m.