Triple
T15885073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lærdal |
E385170
|
entity |
| Predicate | hasPostalCodeCenter |
P93532
|
FINISHED |
| Object | 6887 Lærdal |
—
|
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: 6887 Lærdal | Statement: [Lærdal, hasPostalCodeCenter, 6887 Lærdal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalCodeCenter Context triple: [Lærdal, hasPostalCodeCenter, 6887 Lærdal]
-
A.
postalCodeCenter
chosen
Indicates the central geographic point or representative location associated with a given postal code area.
-
B.
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.
-
C.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
D.
hasPostalFeature
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
E.
alsoServedByPostalCodeSystem
Indicates that the same geographic area or address is additionally covered or identified by another postal code system.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.