Triple
T38578109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briny Breezes, Inc. |
E929462
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | resident-owned corporation |
C30470
|
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: resident-owned corporation Context triple: [Briny Breezes, Inc., instanceOf, resident-owned corporation]
-
A.
resident company
A resident company is a business entity that is legally recognized as being based in a particular country or jurisdiction, typically for tax and regulatory purposes, due to factors such as its place of incorporation, management, or central control.
-
B.
Traditional Owner corporation
A Traditional Owner corporation is a legally recognized entity formed by Indigenous Traditional Owners to represent, manage, and protect their native title rights, cultural heritage, and land-related interests.
-
C.
residential cooperative
chosen
A residential cooperative is a housing arrangement where residents collectively own and manage the property through a cooperative corporation, holding shares that entitle them to occupy specific units.
-
D.
management corporation
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.
-
E.
city corporation
A city corporation is a municipal governing body responsible for administering and managing the infrastructure, public services, and regulatory functions of an urban area.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.