Triple
T25513100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States ZIP code system |
E639434
|
entity |
| Predicate | implementationStartDate |
P288
|
FINISHED |
| Object | 1963-07-01 |
—
|
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: 1963-07-01 | Statement: [United States ZIP code system, implementationStartDate, 1963-07-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationStartDate Context triple: [United States ZIP code system, implementationStartDate, 1963-07-01]
-
A.
implementedProgramStartDate
Indicates the date on which a particular program was put into effect or began operating in practice.
-
B.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
C.
implementationPeriod
Indicates the time span during which a plan, project, or agreement is actively carried out or executed.
-
D.
launchEndDate
Indicates the date on which a launch activity or campaign is completed or comes to an end.
-
E.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
- 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.