Triple
T9185653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chatham community area |
E220450
|
entity |
| Predicate | majorCommercialCorridor |
P30026
|
FINISHED |
| Object | 79th Street |
—
|
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: 79th Street | Statement: [Chatham community area, majorCommercialCorridor, 79th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCommercialCorridor Context triple: [Chatham community area, majorCommercialCorridor, 79th Street]
-
A.
majorUrbanCorridor
Indicates a primary transportation route that connects significant urban areas and supports major flows of people, goods, or services between them.
-
B.
hasMajorRetailCorridor
chosen
Indicates that a place contains or is associated with a primary commercial street or area characterized by a high concentration of retail businesses.
-
C.
hasMajorRailCorridor
Indicates that a location or region is traversed by a primary, high-capacity railway route used for significant passenger or freight transport.
-
D.
transportCorridor
Indicates a route or pathway used to move people, goods, or resources between locations.
-
E.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc318d5c081908c50b56e5783ea38 |
completed | April 1, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:24 p.m.