Triple
T17620442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commissioners' Plan of 1811 |
E429694
|
entity |
| Predicate | geographicExtentNorth |
P13331
|
FINISHED |
| Object | 155th Street |
—
|
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: 155th Street | Statement: [Commissioners' Plan of 1811, geographicExtentNorth, 155th Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicExtentNorth Context triple: [Commissioners' Plan of 1811, geographicExtentNorth, 155th Street]
-
A.
isNorthernmost
Indicates that one entity is located farther north than all other comparable entities in a given set or region.
-
B.
northernBoundaryReference
chosen
Indicates the feature or element that serves as the reference for defining the northern boundary of something.
-
C.
northernBoundaryExtendedTo
Indicates that the northern boundary of one entity has been lengthened or expanded to reach or include another specified reference point or area.
-
D.
formsNorthernExtentOf
Indicates that one entity constitutes or defines the northernmost boundary or limit of another entity.
-
E.
isNorthernmostRegionOf
Indicates that one region is the geographically furthest north among all regions within a specified larger area or entity.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d36074481909ee79e238841edf2 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.