Triple
T20666391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilmore, Ohio |
E507898
|
entity |
| Predicate | postOfficeDiscontinued |
P1466
|
FINISHED |
| Object | 1950 |
—
|
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: 1950 | Statement: [Gilmore, Ohio, postOfficeDiscontinued, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOfficeDiscontinued Context triple: [Gilmore, Ohio, postOfficeDiscontinued, 1950]
-
A.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
B.
previousPostalAdministration
Indicates that one postal administration directly preceded another in responsibility or authority over a given postal service or territory.
-
C.
legalStatusOfPostOffice
Indicates the legal status or standing of a post office within a given jurisdiction or regulatory framework.
-
D.
discontinuedIn
chosen
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
E.
postAbolished
Indicates that a particular official position, office, or post has been formally discontinued and no longer exists.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c39dd48190965d65537592aef6 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.