Triple
T10327131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kokand |
E242787
|
entity |
| Predicate | developedAsUrbanCenter |
P44289
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Kokand, developedAsUrbanCenter, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsUrbanCenter Context triple: [Kokand, developedAsUrbanCenter, 18th century]
-
A.
majorCityOfDevelopment
Indicates that a city is a primary or central location where something (such as a project, product, or technology) is being developed.
-
B.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
-
C.
cityDevelopedBeside
Indicates that a city was developed in close proximity to and along the side of a particular geographic feature, settlement, or infrastructure.
-
D.
notableCityDeveloped
Indicates that a city was significantly developed, expanded, or shaped by the actions, planning, or investment of a particular agent or entity.
-
E.
isUrbanCenter
chosen
Indicates that a place functions as a primary, densely developed hub of population, services, and activities within a 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ce69b881909f27d97c90643634 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:51 a.m.