Triple
T35098890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NY Ave NE |
E1012947
|
entity |
| Predicate | isTransitCorridor |
P3034
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [NY Ave NE, isTransitCorridor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransitCorridor Context triple: [NY Ave NE, isTransitCorridor, yes]
-
A.
isGatewayCorridorFor
Indicates that something serves as a primary access route or passageway enabling movement or connection to another place, system, or area.
-
B.
transportationCorridorType
Indicates the specific kind or classification of a transportation corridor (such as road, rail, or waterway) that characterizes how the route is used for movement or transit.
-
C.
isCoastalCorridor
Indicates that a region or area functions as a continuous coastal passageway connecting different coastal locations.
-
D.
transportCorridor
chosen
Indicates a route or pathway used to move people, goods, or resources between locations.
-
E.
parallelTransportCorridor
Indicates a relationship where one path, route, or connection is used to transport something in a way that preserves its structure or configuration relative to another, typically along a shared or corresponding trajectory.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.