Triple
T27720746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Sand Lake |
E698945
|
entity |
| Predicate | hasZIPCodeSystem |
P7766
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Village of Sand Lake, hasZIPCodeSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZIPCodeSystem Context triple: [Village of Sand Lake, hasZIPCodeSystem, true]
-
A.
postalCodeSystem
chosen
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
B.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
-
C.
hasPostalSystem
Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
-
D.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
E.
hasPostalAddressSystem
Indicates that an entity possesses or is served by an organized system for assigning and managing postal addresses.
- 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6363b50f08190a0d8e16d748388f5 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:06 p.m.