Triple
T16996555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SevenVenues |
E412330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public assembly facilities management division |
C37666
|
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: public assembly facilities management division Context triple: [SevenVenues, instanceOf, public assembly facilities management division]
-
A.
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.
-
B.
asset management company division
A division of an asset management company is an organizational unit responsible for managing specific types of investment products, client segments, or geographic markets within the broader firm.
-
C.
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.
-
D.
maintenance facility
A maintenance facility is a dedicated location equipped with tools, resources, and personnel for inspecting, repairing, and servicing equipment, vehicles, or infrastructure to ensure their proper functioning and longevity.
-
E.
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.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.