Triple
T33522213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleeper, Missouri |
E858534
|
entity |
| Predicate | historicalPostOfficeClosed |
P155701
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [Sleeper, Missouri, historicalPostOfficeClosed, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPostOfficeClosed Context triple: [Sleeper, Missouri, historicalPostOfficeClosed, 1955]
-
A.
postalFunctionCeased
chosen
Indicates that a postal service or function that once operated at a location or entity has been discontinued or is no longer in effect.
-
B.
hadPostOfficeEstablished
Indicates that a post office was officially created or began operating at a given location or for a given entity.
-
C.
previousPostalAdministration
Indicates that one postal administration directly preceded another in responsibility or authority over a given postal service or territory.
-
D.
telegraphStationClosed
Indicates that a telegraph station has ceased operations and is no longer open or functioning.
-
E.
railwayStationClosureDate
Indicates the date on which a railway station was officially closed to service or operations.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 1, 2026, 1:39 a.m.