Triple
T8851510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pike County, Mississippi |
E210647
|
entity |
| Predicate | hasZIPCodeCenter |
P222
|
FINISHED |
| Object | 39648 |
—
|
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: 39648 | Statement: [Pike County, Mississippi, hasZIPCodeCenter, 39648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasZIPCodeCenter Context triple: [Pike County, Mississippi, hasZIPCodeCenter, 39648]
-
A.
zoneCode
Indicates that an entity is associated with, or assigned to, a specific geographic or administrative zone identified by a code.
-
B.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
-
C.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
D.
hasPostalAssociationWith
Indicates a relationship in which one entity is connected to another through postal services, such as mail handling, delivery, routing, or shared postal operations.
-
E.
postalCode
chosen
Indicates the numerical or alphanumerical code assigned to a geographic area for mail delivery associated with an 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c2300c819097b1ca6ebe2f749a |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.