Triple
T4164112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NP7 |
E84399
|
entity |
| Predicate | hasPostcodeFormat |
P54205
|
FINISHED |
| Object | NP7 nnn |
—
|
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: NP7 nnn | Statement: [NP7, hasPostcodeFormat, NP7 nnn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostcodeFormat Context triple: [NP7, hasPostcodeFormat, NP7 nnn]
-
A.
hasPostalCodePrefix
Indicates that a location’s postal code begins with a specified sequence of characters.
-
B.
hasPostalFeature
Indicates that one entity possesses, includes, or is characterized by a specific postal-related feature (such as a code, service, or facility).
-
C.
postalCodeSystem
Indicates a system that assigns structured postal codes to geographic areas for organizing and routing mail.
-
D.
hasPostalSystem
Indicates that an entity possesses or operates an organized system for sending, receiving, and delivering mail or parcels.
-
E.
hasPostalCountryCode
Indicates that an entity is associated with a specific country code used for postal addressing or mail routing.
- F. None of above. chosen
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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0320775c8190b90d80f512060f1c |
completed | March 9, 2026, 5:28 p.m. |
Created at: March 9, 2026, 3:44 p.m.