Triple
T22036324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakhmach |
E544217
|
entity |
| Predicate | wasIncorporatedAsTown |
P3881
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Bakhmach, wasIncorporatedAsTown, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasIncorporatedAsTown Context triple: [Bakhmach, wasIncorporatedAsTown, 20th century]
-
A.
incorporatedAsTownIn
chosen
Indicates that an entity was officially established and given legal status as a town within a specified jurisdiction.
-
B.
incorporatedAsTownship
Indicates that an area or community has been formally established and recognized as a township through a legal or governmental incorporation process.
-
C.
wasFoundedAsTown
Indicates that an entity came into existence specifically with the legal or formal status of a town.
-
D.
isFormerlyUnincorporated
Indicates that an entity previously had the legal or administrative status of being unincorporated but has since become incorporated.
-
E.
incorporatedAsMunicipality
Indicates that an area or settlement has been legally established and recognized as a municipality through a formal incorporation process.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f1f95c8190a324c84313cd91ee |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.