Triple
T6196867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Community District 6 |
E138529
|
entity |
| Predicate | sideOfManhattan |
P56861
|
FINISHED |
| Object | East Side |
—
|
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: East Side | Statement: [Manhattan Community District 6, sideOfManhattan, East Side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOfManhattan Context triple: [Manhattan Community District 6, sideOfManhattan, East Side]
-
A.
onSideOfManhattan
chosen
Indicates that one entity is located on the same side of Manhattan as, or relative to, another reference entity.
-
B.
ManhattanPortalLocatedIn
Indicates that a specific portal or gateway is situated within the geographic area of Manhattan.
-
C.
manhattanConnection
Indicates a direct or indirect connection or route between two entities specifically within the Manhattan area or grid.
-
D.
terminusInManhattan
Indicates that the endpoint or final stop of something (such as a route, line, or service) is located within Manhattan.
-
E.
primaryManhattanLine
Indicates that one line segment or path is the main or dominant axis, measured using Manhattan (grid-based) distance, relative to other possible lines.
- 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_69c008ab9b3081908a11b2c744838435 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062508f5c8190a00291708a9a7de9 |
completed | March 22, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c055fbce1081908805fd12e242ab96 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.