Triple
T31621159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facilities and Property Management |
E806898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state facilities management organization |
C60901
|
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: state facilities management organization Context triple: [Facilities and Property Management, instanceOf, state facilities management organization]
-
A.
administrative facility portfolio
A coordinated collection of administrative facilities managed as a unified asset set to support organizational operations, planning, and strategic decision-making.
-
B.
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.
-
C.
public assembly facilities management division
The public assembly facilities management division oversees the operation, maintenance, scheduling, and safety of venues where large groups gather, such as convention centers, arenas, and public event spaces.
-
D.
military installation management organization
A military installation management organization is an entity responsible for planning, operating, maintaining, and supporting the infrastructure, services, and resources of one or more military bases to ensure mission readiness and quality of life for personnel.
-
E.
business facility group
A business facility group is a collection of related physical or virtual business premises managed together for coordinated operations, services, or administration.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:41 p.m.