Triple
T34637515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Street (Bristol) |
E889468
|
entity |
| Predicate | hasPostalCodesOnSides |
P186447
|
FINISHED |
| Object | Tennessee ZIP codes |
—
|
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: Tennessee ZIP codes | Statement: [State Street (Bristol), hasPostalCodesOnSides, Tennessee ZIP codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalCodesOnSides Context triple: [State Street (Bristol), hasPostalCodesOnSides, Tennessee ZIP codes]
-
A.
hasPostalFeature
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
B.
hasPostcodeAreasAlong
chosen
Indicates that a geographic feature or route is associated with, or passes through, specific postcode areas along its extent.
-
C.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
-
D.
sharePostalSystemElements
Indicates that two entities use or have in common specific components or features of the same postal system.
-
E.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 1, 2026, 2:04 a.m.