Triple
T28632524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welper |
E724681
|
entity |
| Predicate | sharesPostalCodeWith |
P136734
|
FINISHED |
| Object | Hattingen |
—
|
NE NERFINISHED |
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: Hattingen | Statement: [Welper, sharesPostalCodeWith, Hattingen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesPostalCodeWith Context triple: [Welper, sharesPostalCodeWith, Hattingen]
-
A.
sharesZIPCodeWith
chosen
Indicates that two entities are located in areas that have the same ZIP or postal code.
-
B.
postalServiceSharedWith
Indicates that two or more entities use or are served by the same postal service or postal delivery system.
-
C.
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.
-
D.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 28, 2026, 4:38 a.m.