Triple
T30560960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McPaul, Iowa |
E777838
|
entity |
| Predicate | hasPostalHistory |
P195644
|
FINISHED |
| Object | former post office |
—
|
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: former post office | Statement: [McPaul, Iowa, hasPostalHistory, former post office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPostalHistory Context triple: [McPaul, Iowa, hasPostalHistory, former post office]
-
A.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
B.
hasPostalServiceStatus
Indicates the current operational or service condition of a postal service for a given entity or location.
-
C.
hasPostalSuccessor
Indicates that one postal entity directly follows another in an ordered postal sequence, such as in routing, numbering, or service succession.
-
D.
hadPostOffice
Indicates that a place or entity possessed or was served by an official post office facility.
-
E.
hasPostalAuthority
Indicates that an entity possesses official authority or jurisdiction over postal services or mail operations for a given area or context.
- F. None of above. chosen
Provenance (4 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: April 29, 2026, 8:21 p.m.