Triple
T35392312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Heerenveen |
E1022972
|
entity |
| Predicate | postalCodeRangeCountry |
P476
|
FINISHED |
| Object | Netherlands |
E864
|
NE 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: Netherlands | Statement: [municipality of Heerenveen, postalCodeRangeCountry, Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalCodeRangeCountry Context triple: [municipality of Heerenveen, postalCodeRangeCountry, Netherlands]
-
A.
postalCodeRange
chosen
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
B.
postalCodeInCountry
Indicates that a given postal code is assigned to and valid within a particular country.
-
C.
postalAreaIncludes
Indicates that a given postal area geographically contains or covers another specified location or region.
-
D.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
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 (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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794fd5fd08190ab39a0c8882536df |
completed | May 3, 2026, 6:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a382ca6a83c8190bff490b5034abb48 |
completed | June 21, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.