Triple
T33522212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleeper, Missouri |
E858534
|
entity |
| Predicate | historicalPostOfficeEstablished |
P142417
|
FINISHED |
| Object | 1883 |
—
|
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: 1883 | Statement: [Sleeper, Missouri, historicalPostOfficeEstablished, 1883]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPostOfficeEstablished Context triple: [Sleeper, Missouri, historicalPostOfficeEstablished, 1883]
-
A.
hadPostOfficeEstablished
chosen
Indicates that a post office was officially created or began operating at a given location or for a given entity.
-
B.
placeEstablished
Indicates that an entity was founded, created, or formally established at a particular place or location.
-
C.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
-
D.
hadPostOffice
Indicates that a place or entity possessed or was served by an official post office facility.
-
E.
municipalityEstablished
Indicates that a municipality was officially created or founded at a specific point in time.
- 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_6a000a1d8fa88190a1d82ac746565c48 |
completed | May 10, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_6a0008b26eb88190ae03b2309a614774 |
completed | May 10, 2026, 4:25 a.m. |
Created at: May 1, 2026, 1:39 a.m.