Triple
T8041050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Navy Yard (south end) |
E187439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mixed-use campus |
C726
|
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: mixed-use campus Context triple: [Philadelphia Navy Yard (south end), instanceOf, mixed-use campus]
-
A.
multi-campus university
A multi-campus university is an institution of higher education that operates multiple geographically separate campuses under a single administrative and academic governance structure.
-
B.
mixed-use development district
chosen
A mixed-use development district is a designated urban area that intentionally combines residential, commercial, recreational, and sometimes industrial uses within a walkable, integrated environment to promote vibrant, efficient, and sustainable community life.
-
C.
mixed-use lifestyle center
A mixed-use lifestyle center is a planned development that combines retail, dining, entertainment, residential, and often office spaces in a walkable, open-air environment designed to create a vibrant, community-oriented destination.
-
D.
multi-campus university structure
A multi-campus university structure is an organizational framework in which a single university operates multiple geographically dispersed campuses that share governance, academic standards, and resources while serving distinct local communities and programmatic needs.
-
E.
campus
A campus is a defined area of land that houses the buildings, facilities, and open spaces of an educational institution, supporting academic, residential, and social activities.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:23 p.m.