Triple
T11460031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windsor Mill, Maryland |
E271629
|
entity |
| Predicate | postalServiceAreaIncludes |
P32592
|
FINISHED |
| Object | ZIP Code 21244 |
—
|
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: ZIP Code 21244 | Statement: [Windsor Mill, Maryland, postalServiceAreaIncludes, ZIP Code 21244]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalServiceAreaIncludes Context triple: [Windsor Mill, Maryland, postalServiceAreaIncludes, ZIP Code 21244]
-
A.
postalAreaIncludes
chosen
Indicates that a given postal area geographically contains or covers another specified location or region.
-
B.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
C.
hasPostalRole
Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
-
D.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
E.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
- 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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f2138081909408c7916cef99c9 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.