Triple
T6210205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorpommern-Rügen |
E138846
|
entity |
| Predicate | usesPostalCodeRange |
P476
|
FINISHED |
| Object | 18311–18589 |
—
|
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: 18311–18589 | Statement: [Vorpommern-Rügen, usesPostalCodeRange, 18311–18589]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPostalCodeRange Context triple: [Vorpommern-Rügen, usesPostalCodeRange, 18311–18589]
-
A.
postalCodeRange
chosen
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
B.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
C.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
D.
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.
-
E.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062896f3881909f264bb45badc5d0 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.