Triple
T33713153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ski municipality |
E863795
|
entity |
| Predicate | hadPostalCodeCentre |
P93532
|
FINISHED |
| Object | 1400 Ski |
—
|
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: 1400 Ski | Statement: [Ski municipality, hadPostalCodeCentre, 1400 Ski]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPostalCodeCentre Context triple: [Ski municipality, hadPostalCodeCentre, 1400 Ski]
-
A.
postalCodeCenter
chosen
Indicates the central geographic point or representative location associated with a given postal code area.
-
B.
isCentralPostalDistrict
Indicates that a given postal district serves as the primary or central postal area within a city or region.
-
C.
hasPostcodeDistrictCode
Indicates that an entity is associated with a specific postcode district code within a postal addressing system.
-
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.
postalCode
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fabe07848190bd4f14ac6dfa35b6 |
completed | May 3, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.