Triple
T25513096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States ZIP code system |
E639434
|
entity |
| Predicate | extendedCodeLength |
P70662
|
FINISHED |
| Object | 9 digits |
—
|
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: 9 digits | Statement: [United States ZIP code system, extendedCodeLength, 9 digits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedCodeLength Context triple: [United States ZIP code system, extendedCodeLength, 9 digits]
-
A.
blockCodeLengthFormula
Indicates a relationship where a formula specifies how to compute the length of a block of code.
-
B.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
C.
scriptCodeLength
Indicates the length or number of characters in a given script or code sequence.
-
D.
definesCodeUnitSequenceLength
chosen
Indicates that an entity specifies or determines the length of a sequence of code units (such as characters or encoded units) for another entity.
-
E.
extendedFor
Indicates that something has been lengthened in duration, scope, or extent specifically for the benefit or use of another entity.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f82fe30881909915c13a183be6c3 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:53 p.m.