Triple
T19791160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Francisco Tourism Improvement District Management Corporation |
E475411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | management corporation |
C42628
|
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: management corporation Context triple: [San Francisco Tourism Improvement District Management Corporation, instanceOf, management corporation]
-
A.
private management company
A private management company is a non-governmental organization that provides professional administrative, operational, and strategic management services to businesses, properties, or assets, typically for a fee.
-
B.
estate management office
An estate management office is an administrative unit responsible for overseeing, maintaining, and coordinating the operations, finances, and services of a property or group of properties.
-
C.
facility management company
A facility management company is an organization that plans, operates, and maintains buildings and their services to ensure safe, efficient, and cost-effective environments for occupants and owners.
-
D.
infrastructure management company
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
E.
ownership company
An ownership company is a legal entity that holds and manages ownership stakes in assets or other businesses, exercising control and deriving benefits from those holdings.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:49 p.m.