Triple
T22113939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFV |
E546488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | property management organization |
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: property management organization Context triple: [SFV, instanceOf, property management organization]
-
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.
management corporation
chosen
A management corporation is a legal entity formed to oversee, administer, and coordinate the operations, assets, or services of one or more organizations, properties, or projects on behalf of owners or stakeholders.
-
C.
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.
-
D.
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.
-
E.
business improvement district management organization
A business improvement district management organization is an entity, typically a nonprofit or quasi-public body, that administers and funds enhanced services and improvements within a defined commercial area using assessments collected from local property or business owners.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:31 p.m.