Triple
T27815249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAP headquarters campus |
E702642
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | corporate headquarters campus |
C400
|
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: corporate headquarters campus Context triple: [SAP headquarters campus, instanceOf, corporate headquarters campus]
-
A.
former corporate headquarters
A former corporate headquarters is a building or complex that once served as the primary administrative and executive center for a corporation but no longer fulfills that role.
-
B.
headquarters
chosen
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
C.
science and business campus
A science and business campus is an integrated environment where research facilities, academic institutions, and commercial enterprises co-locate to foster innovation, collaboration, and the translation of scientific discoveries into marketable solutions.
-
D.
office building complex
An office building complex is a group of interconnected or closely situated office structures designed to provide workspace, shared amenities, and supporting services for multiple businesses or organizations.
-
E.
university system headquarters
The university system headquarters is the central administrative entity that oversees, coordinates, and supports the policies, operations, and strategic direction of all institutions within a multi-campus university system.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
Created at: April 27, 2026, 5:45 p.m.