Triple
T23931753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 37 |
E602516
|
entity |
| Predicate | hasPrimaryStreetFrontage |
P106122
|
FINISHED |
| Object | State 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: State Street | Statement: [Block 37, hasPrimaryStreetFrontage, State Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryStreetFrontage Context triple: [Block 37, hasPrimaryStreetFrontage, State Street]
-
A.
hasStreetFront
Indicates that one entity directly borders or faces onto a particular street along its frontage.
-
B.
hasFrontageRoads
Indicates that a primary road or highway is accompanied by one or more adjacent frontage roads running alongside it.
-
C.
streetFrontageOn
chosen
Indicates that a property or parcel directly borders or faces a particular street along at least one of its sides.
-
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.
hasMainResidentialStreet
Indicates that an entity is associated with or served by a specific primary street used predominantly for residential purposes.
- 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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cf9c223881908e5fa4b5564848e6 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.