Triple
T29355336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Fordham Road |
E744424
|
entity |
| Predicate | hasRoleInBronx |
P186372
|
FINISHED |
| Object | primary east–west corridor |
—
|
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: primary east–west corridor | Statement: [East Fordham Road, hasRoleInBronx, primary east–west corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInBronx Context triple: [East Fordham Road, hasRoleInBronx, primary east–west corridor]
-
A.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
B.
hasBoroughPresidentJurisdiction
Indicates that a borough president has official authority or administrative jurisdiction over a specified geographic or political area.
-
C.
usesTrunkLineInBronx
Indicates that an entity makes use of a trunk (primary) transportation or utility line located in the Bronx.
-
D.
hasBoroughOrNeighborhood
Indicates that a place is located within, or associated with, a specific borough or neighborhood.
-
E.
wasBoroughOf
Indicates that one place previously held the administrative or territorial status of a borough within another jurisdiction.
- F. None of above. chosen
Provenance (4 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 28, 2026, 2:11 p.m.