Triple
T33673941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veggli |
E862704
|
entity |
| Predicate | hasPostalCodeNumber |
P178718
|
FINISHED |
| Object | 3628 |
—
|
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: 3628 | Statement: [Veggli, hasPostalCodeNumber, 3628]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalCodeNumber Context triple: [Veggli, hasPostalCodeNumber, 3628]
-
A.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
B.
isPostalCode
chosen
Indicates that one entity is a valid postal (ZIP) code assigned to identify the geographic area of the other entity.
-
C.
hasPostalFeature
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
D.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
-
E.
hasPostalRole
Indicates that an entity holds or is assigned a specific role or function within a postal or mail-related context.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
Created at: May 1, 2026, 1:43 a.m.