Triple
T24339501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SO36 |
E613473
|
entity |
| Predicate | postalCodeOrigin |
P155769
|
FINISHED |
| Object | old Berlin postal district SO 36 |
—
|
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: old Berlin postal district SO 36 | Statement: [SO36, postalCodeOrigin, old Berlin postal district SO 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalCodeOrigin Context triple: [SO36, postalCodeOrigin, old Berlin postal district SO 36]
-
A.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an entity.
-
B.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
C.
postalName
Indicates the standardized name or label used for addressing and postal purposes associated with an entity.
-
D.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
E.
postalCodeType
Indicates the classification or type category assigned to a given postal code.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932324e8819082344cf42eddc274 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:57 a.m.