Triple
T37270533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capitol Crossing |
E924500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | air rights development |
C65408
|
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: air rights development Context triple: [Capitol Crossing, instanceOf, air rights development]
-
A.
property development joint venture
A property development joint venture is a collaborative business arrangement in which two or more parties pool capital, expertise, and resources to plan, finance, develop, and sometimes operate a real estate project while sharing risks, costs, and returns.
-
B.
high-rise development program
A high-rise development program is a coordinated set of policies, plans, and projects that guide the financing, design, construction, and long-term management of tall multi-story buildings within a defined urban area.
-
C.
luxury real estate development
A luxury real estate development is a high-end property project that combines premium locations, superior design and construction, and exclusive amenities to deliver an elevated living or investment experience for affluent buyers.
-
D.
aerotropolis
An aerotropolis is an urban development model in which a major airport functions as the central hub around which business, residential, and logistics districts are planned and built.
-
E.
airport investment company
An airport investment company is a business entity that finances, owns, or manages stakes in airports and related infrastructure to generate returns through aviation operations, concessions, and long-term asset appreciation.
- 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.