Triple
T38487117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facilities Services Directorate |
E917947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | facilities management organization |
C21132
|
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: facilities management organization Context triple: [Facilities Services Directorate, instanceOf, facilities management organization]
-
A.
facility management company
chosen
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.
state facilities management organization
A state facilities management organization is a government entity responsible for planning, operating, maintaining, and optimizing the physical buildings and infrastructure owned or leased by a state.
-
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.
management firm
A management firm is an organization that provides professional planning, coordination, and oversight services to help clients efficiently run and grow their businesses or projects.
-
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.
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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:31 p.m.