Triple
T22642753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CEP |
E558873
|
entity |
| Predicate | regionEncoding |
P3820
|
FINISHED |
| Object | first digit indicates postal region |
—
|
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: first digit indicates postal region | Statement: [CEP, regionEncoding, first digit indicates postal region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionEncoding Context triple: [CEP, regionEncoding, first digit indicates postal region]
-
A.
zoneNameEncoding
Indicates how the name of a zone is represented or encoded in a specific format or scheme.
-
B.
regionCodeType
chosen
Indicates the classification or format type used for a given region code within a coding or identification system.
-
C.
regionCodeLevel
Indicates the hierarchical level or granularity associated with a given regional code within an administrative or geographic coding system.
-
D.
regionSetting
Indicates that an entity is configured to operate within, or is associated with, a specific geographic or logical region.
-
E.
longitudeRegion
Indicates that an entity is located within or associated with a specific longitudinal region on the Earth’s surface.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703577948190ae044df4f8500bfe |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.