Triple
T25101216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smithton, Missouri |
E628727
|
entity |
| Predicate | originalTownSiteOf |
P3028
|
FINISHED |
| Object | Columbia, Missouri |
—
|
NE NERFINISHED |
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: Columbia, Missouri | Statement: [Smithton, Missouri, originalTownSiteOf, Columbia, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTownSiteOf Context triple: [Smithton, Missouri, originalTownSiteOf, Columbia, Missouri]
-
A.
originalSettlement
chosen
Indicates that one entity is the initial or first-established settlement location associated with another entity.
-
B.
originalSettlementName
Indicates the name by which a settlement was originally known before any later renaming or reclassification.
-
C.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
-
D.
originalSiteArea
Indicates the total land area of the site in its initial or pre-modified state.
-
E.
primaryTown
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 18, 2026, 6:25 a.m.