Triple
T37607450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 430 Park Avenue |
E935692
|
entity |
| Predicate | hasStreetFrontageOn |
P106122
|
FINISHED |
| Object | Park Avenue |
—
|
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: Park Avenue | Statement: [430 Park Avenue, hasStreetFrontageOn, Park Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetFrontageOn Context triple: [430 Park Avenue, hasStreetFrontageOn, Park Avenue]
-
A.
hasStreetFront
Indicates that one entity directly borders or faces onto a particular street along its frontage.
-
B.
streetFrontageOn
chosen
Indicates that a property or parcel directly borders or faces a particular street along at least one of its sides.
-
C.
hasFrontageRoads
Indicates that a primary road or highway is accompanied by one or more adjacent frontage roads running alongside it.
-
D.
hasTypicalFrontage
Indicates that something normally faces or fronts onto something else, such as a property having its usual frontage on a particular street or area.
-
E.
hasBuildingUseAlongStreet
Indicates that a building located along a particular street is used for a specified purpose or function in relation to that street.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
Created at: May 3, 2026, 4:18 p.m.