Triple
T4550084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyonaka Campus |
E110140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | campus of Osaka University |
C17161
|
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: campus of Osaka University Context triple: [Toyonaka Campus, instanceOf, campus of Osaka University]
-
A.
Nagoya University campus
Nagoya University campus is a sprawling, research-focused academic environment in Nagoya, Japan, featuring modern facilities, green spaces, and a blend of traditional and contemporary architecture that supports education, innovation, and student life.
-
B.
Osaka University research institute
An Osaka University research institute is an academic organization within Osaka University dedicated to advancing specialized fields of study through research, collaboration, and education.
-
C.
Tohoku University campus
Tohoku University campus is a sprawling, research-focused academic environment in Sendai, Japan, blending modern laboratories and facilities with green spaces and traditional architecture to support education, innovation, and student life.
-
D.
constituent school of Osaka University
A constituent school of Osaka University is an academic unit or faculty that operates under the university’s governance, offering specialized education and research programs within a particular discipline.
-
E.
Shenzhen University campus
Shenzhen University campus is a modern, green, and coastal urban campus in Shenzhen, China, known for its innovative architecture, lush landscapes, and integration with the surrounding tech-driven city.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:05 p.m.