Triple
T26914322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshimoto Kogyo Osaka headquarters |
E677476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoshimoto Kogyo facility |
C52205
|
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: Yoshimoto Kogyo facility Context triple: [Yoshimoto Kogyo Osaka headquarters, instanceOf, Yoshimoto Kogyo facility]
-
A.
Osaka Metro facility
An Osaka Metro facility is any physical structure, station, depot, or related infrastructure owned or operated by Osaka Metro that supports the operation, maintenance, or use of its urban rail transit system.
-
B.
Toyota Motor Corporation facility
A Toyota Motor Corporation facility is any physical site owned or operated by Toyota where activities such as vehicle manufacturing, research and development, logistics, administration, sales, or service are conducted in support of the company’s automotive business.
-
C.
JAXA facility
A JAXA facility is a physical site operated by the Japan Aerospace Exploration Agency that supports space-related research, development, testing, mission control, or public outreach activities.
-
D.
Tōkaidō post station
A Tōkaidō post station was an officially designated rest and relay point along Japan’s historic Tōkaidō road, providing lodging, services, and logistical support for travelers, officials, and goods between Edo and Kyoto.
-
E.
Ichinomiya
Ichinomiya is a conceptual class representing the highest-ranked Shinto shrine in a historical Japanese province, often serving as a central religious and cultural institution for the region.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:03 a.m.