Triple
T34861393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marble Hill–225th Street |
E1004881
|
entity |
| Predicate | hasBoroughBorderContext |
P194822
|
FINISHED |
| Object | near boundary of Manhattan and the Bronx |
—
|
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: near boundary of Manhattan and the Bronx | Statement: [Marble Hill–225th Street, hasBoroughBorderContext, near boundary of Manhattan and the Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoroughBorderContext Context triple: [Marble Hill–225th Street, hasBoroughBorderContext, near boundary of Manhattan and the Bronx]
-
A.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
-
B.
hasNearbyBorough
Indicates that one borough is geographically close to or adjacent to another borough.
-
C.
hasBoroughSegment
Indicates that something is a specific segment or portion within a larger borough.
-
D.
isBorderDistrict
Indicates that a district is located along and directly borders the boundary of a larger administrative region or country.
-
E.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4 p.m.