Triple
T35796781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3 Seventh Avenue Express |
E1034855
|
entity |
| Predicate | traversesBoroughs |
P21450
|
FINISHED |
| Object | Brooklyn–Manhattan–The Bronx |
—
|
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: Brooklyn–Manhattan–The Bronx | Statement: [3 Seventh Avenue Express, traversesBoroughs, Brooklyn–Manhattan–The Bronx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversesBoroughs Context triple: [3 Seventh Avenue Express, traversesBoroughs, Brooklyn–Manhattan–The Bronx]
-
A.
passesThroughBorough
chosen
Indicates that something (such as a route, line, or path) traverses or goes through a particular borough.
-
B.
hasBoroughEndpoint
Indicates that something has an endpoint located within a specific borough.
-
C.
connectsBoroughsOf
Indicates a relationship where something serves as a link or route joining two or more boroughs to each other.
-
D.
crossesBoroughFeature
Indicates that one entity extends across or passes through a geographic feature that spans multiple boroughs.
-
E.
hasBorough
Indicates that one entity is located within, belongs to, or is administratively part of a specific borough.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.