Triple
T7782017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keene, California |
E221542
|
entity |
| Predicate | postOfficeOpened |
P43960
|
FINISHED |
| Object | 1879 |
—
|
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: 1879 | Statement: [Keene, California, postOfficeOpened, 1879]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postOfficeOpened Context triple: [Keene, California, postOfficeOpened, 1879]
-
A.
municipalOfficesOpened
Indicates that municipal government offices have begun operating or have been officially opened for public service.
-
B.
openingTime
chosen
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
openPitClosedIn
Indicates that an open-pit mine or excavation has been closed, decommissioned, or otherwise taken out of active use at a specified time or under specified conditions.
-
D.
operatedPostOfficesIn
Indicates that one entity managed and ran the functioning of post office locations within the domain or area of another entity.
-
E.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:21 p.m.