Triple
T20998094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colfax, Texas |
E517203
|
entity |
| Predicate | hadPostOfficeEstablished |
P142417
|
FINISHED |
| Object | 1870s |
—
|
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: 1870s | Statement: [Colfax, Texas, hadPostOfficeEstablished, 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPostOfficeEstablished Context triple: [Colfax, Texas, hadPostOfficeEstablished, 1870s]
-
A.
hasPostalServiceThrough
Indicates that one entity receives or provides postal services by means of, or via the infrastructure of, another entity.
-
B.
establishedAsArmyPost
Indicates that a location or site was formally designated and set up to function as a military post or army installation.
-
C.
hasPostalHeadOffice
Indicates that an entity has a specific location serving as its main or primary postal head office.
-
D.
foundedAfterArrivalOf
Indicates that one entity was founded only after the arrival or appearance of another specified entity.
-
E.
placeEstablished
Indicates that an entity was founded, created, or formally established at a particular place or location.
- F. None of above. chosen
Provenance (4 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_69e0b5006e2881909fc2383f841740cc |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc22ca6081908bf054ddcfea9e19 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:51 p.m.