Triple
T32000211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qashliq |
E817104
|
entity |
| Predicate | usedAsCapitalInCentury |
P194562
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Qashliq, usedAsCapitalInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCapitalInCentury Context triple: [Qashliq, usedAsCapitalInCentury, 16th century]
-
A.
abandonedAsCapitalInCentury
Indicates that a city or settlement ceased to function as a capital during the specified century.
-
B.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
-
C.
usedCapitalAs
Indicates that one entity employed another entity as financial capital or funding in carrying out an action or achieving a result.
-
D.
usedAsMintInCentury
Indicates that an entity functioned as a mint (coin-producing facility) during a specified century.
-
E.
usedCapital
Indicates that an entity made use of a particular capital city as its seat of government or primary administrative center.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69fd7b042a548190b3abe31bc3258278 |
completed | May 8, 2026, 5:56 a.m. |
Created at: May 1, 2026, 12:14 a.m.