Triple
T26279999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzgen |
E660676
|
entity |
| Predicate | wasMajorCenterOn |
P164
|
FINISHED |
| Object | Silk Road |
—
|
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: Silk Road | Statement: [Uzgen, wasMajorCenterOn, Silk Road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorCenterOn Context triple: [Uzgen, wasMajorCenterOn, Silk Road]
-
A.
wasMajorCenterDuring
Indicates that a place served as a primary or highly significant hub of activity, influence, or importance during a specified time period.
-
B.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
C.
isMajorRegionalCenter
Indicates that a location functions as a primary hub of economic, administrative, or cultural activity within a specific geographic region.
-
D.
isMajorResidentialCenterOf
Indicates that a location serves as a primary hub or main area of residence for the referenced population or region.
-
E.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e734a088190ae453cc5dd222b40 |
completed | May 2, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:59 p.m.