Triple
T21577543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue U |
E532436
|
entity |
| Predicate | hasZIPCodeAlongRoute |
P144327
|
FINISHED |
| Object | 11223 |
—
|
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: 11223 | Statement: [Avenue U, hasZIPCodeAlongRoute, 11223]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZIPCodeAlongRoute Context triple: [Avenue U, hasZIPCodeAlongRoute, 11223]
-
A.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
B.
approximateRouteLength
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
C.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
D.
rangeHighwayApprox
Indicates that one entity is approximately within the range or vicinity of a highway associated with another entity.
-
E.
zoningAlong
Indicates that one entity’s zoning designation applies to or runs alongside the boundary, corridor, or extent of another entity (such as a road, parcel, or geographic feature).
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb59cee08190aae55ad6e2a4e077 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:31 p.m.