Triple
T18537212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Straight Path (road) |
E452994
|
entity |
| Predicate | hasZIPCodesAlong |
P32512
|
FINISHED |
| Object | 11798 |
—
|
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: 11798 | Statement: [Straight Path (road), hasZIPCodesAlong, 11798]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZIPCodesAlong Context triple: [Straight Path (road), hasZIPCodesAlong, 11798]
-
A.
hasPostalAssociationWith
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
-
B.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
C.
hasPostalFeature
chosen
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
D.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
-
E.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5340256d08190bf22d2cb064413b2 |
completed | April 19, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.