Triple
T34549745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Código Postal de México |
E887028
|
entity |
| Predicate | typicalFormatExample |
—
|
GENERATED |
| Object | 01000 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFormatExample Context triple: [Código Postal de México, typicalFormatExample, 01000]
-
A.
typicalUsageFormat
Indicates the usual or standard way in which something is expressed, presented, or formatted in practice.
-
B.
valueFormatExample
chosen
Indicates an example of how a value should be formatted or represented.
-
C.
typicalFinalFormat
Indicates that something represents the usual or standard structure or arrangement in which an item, document, or data is ultimately presented or delivered.
-
D.
typicalRecognitionFormat
Indicates the usual or standard format in which something is recognized, identified, or acknowledged.
-
E.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
- F. None of above.
Provenance (1 batch)
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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.