Triple
T2219085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Center |
E48098
|
entity |
| Predicate | hasPublicSpaces |
P37084
|
FINISHED |
| Object | plazas and concourses |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: plazas and concourses | Statement: [Penn Center, hasPublicSpaces, plazas and concourses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpaces Context triple: [Penn Center, hasPublicSpaces, plazas and concourses]
-
A.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
B.
isPublicBuilding
Indicates that a building is designated for public use, access, or service rather than being privately owned or restricted.
-
C.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
-
D.
hasPublicHouse
Indicates that one entity possesses, operates, or is associated with a public house (such as a bar or pub) as part of its facilities or holdings.
-
E.
hasPublicLibraryBuilding
Indicates that an entity possesses or is associated with a public library building as a physical facility.
- F. None of above. chosen
Provenance (4 batches)
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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbfe93d7c81909f1b9c1b1e3c7989 |
completed | March 7, 2026, 6:04 a.m. |
Created at: March 4, 2026, 7:46 p.m.