Triple
T27984577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grand Old Lady of Locust Street |
E706708
|
entity |
| Predicate | hasMainFacadeOn |
P107126
|
FINISHED |
| Object | South Broad Street |
—
|
NE NERFINISHED |
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: South Broad Street | Statement: [The Grand Old Lady of Locust Street, hasMainFacadeOn, South Broad Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainFacadeOn Context triple: [The Grand Old Lady of Locust Street, hasMainFacadeOn, South Broad Street]
-
A.
hasFacadeBy
Indicates that one entity’s façade (front-facing exterior surface) is designed, created, or provided by another entity.
-
B.
hasFacadeSystem
Indicates that one entity possesses or is equipped with a particular façade system as part of its structure or design.
-
C.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
D.
hasMainArch
Indicates that an entity possesses or features a primary or central arch structure.
-
E.
mainFacadeFaces
chosen
Indicates that the primary front facade of a structure is oriented toward or directed at a particular side, direction, or reference point.
- F. None of above.
Provenance (3 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 27, 2026, 7:46 p.m.