Triple
T25513126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States ZIP code system |
E639434
|
entity |
| Predicate | doesNotAlwaysAlignWith |
P126902
|
FINISHED |
| Object | city boundaries |
—
|
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: city boundaries | Statement: [United States ZIP code system, doesNotAlwaysAlignWith, city boundaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotAlwaysAlignWith Context triple: [United States ZIP code system, doesNotAlwaysAlignWith, city boundaries]
-
A.
notAlignedWith
Indicates that one entity’s position, orientation, or viewpoint does not correspond or agree with that of another entity.
-
B.
sometimesAlignedAs
chosen
Indicates that two entities are occasionally in agreement, coordination, or matching orientation, but not consistently or permanently.
-
C.
doesNotInterlineWith
Indicates that two elements, such as routes or services, do not share a common segment or coordinated connection for through-service or transfer.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
notCoterminousWith
Indicates that two entities do not share the same boundaries in space, time, or extent and therefore are not exactly coincident.
- 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_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:53 p.m.