Triple
T30342595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE Tokyo Section |
E771796
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional branch of IEEE |
C173
|
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 branch of IEEE Context triple: [IEEE Tokyo Section, instanceOf, regional branch of IEEE]
-
A.
division of IEEE
A division of IEEE is a specialized organizational unit within the Institute of Electrical and Electronics Engineers that focuses on advancing a particular technical field or professional area through standards, publications, conferences, and member activities.
-
B.
organizational unit of IEEE
chosen
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
-
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 scientific body
A regional scientific body is an organization that coordinates, supports, and promotes scientific research, collaboration, and policy advice within a specific geographic region.
-
E.
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.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:55 p.m.