Triple
T27384400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eskridge, Kansas |
E691325
|
entity |
| Predicate | postalServiceEstablishedInYear |
P142417
|
FINISHED |
| Object | 1868 |
—
|
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: 1868 | Statement: [Eskridge, Kansas, postalServiceEstablishedInYear, 1868]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalServiceEstablishedInYear Context triple: [Eskridge, Kansas, postalServiceEstablishedInYear, 1868]
-
A.
hadPostOfficeEstablished
chosen
Indicates that a post office was officially created or began operating at a given location or for a given entity.
-
B.
introducedPostalSystemInState
Indicates that an entity established or initiated a postal system within a particular state.
-
C.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
D.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
E.
eraOfEstablishment
Indicates the time period or historical era during which an entity was founded or established.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62c89b7b88190a8b2af842f5f9cca |
completed | May 2, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:23 p.m.