Triple
T34607329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aduard (former municipality) |
E888628
|
entity |
| Predicate | hadPostalCodeRegion |
P920
|
FINISHED |
| Object | 9831 (Aduard area) |
—
|
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: 9831 (Aduard area) | Statement: [Aduard (former municipality), hadPostalCodeRegion, 9831 (Aduard area)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPostalCodeRegion Context triple: [Aduard (former municipality), hadPostalCodeRegion, 9831 (Aduard area)]
-
A.
hasPostalAddressRegion
Indicates the region component (such as state, province, or area) associated with an entity’s postal address.
-
B.
postalRegionOf
Indicates that a given area or zone serves as the designated postal region for another location or address.
-
C.
postalArea
chosen
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
-
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.
hadPostalAbbreviation
Indicates that an entity was associated with a specific official postal abbreviation at some time.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.