Triple
T38378634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrgyzstan Time |
E893694
|
entity |
| Predicate | introducedAsSingleZone |
P199081
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Kyrgyzstan Time, introducedAsSingleZone, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsSingleZone Context triple: [Kyrgyzstan Time, introducedAsSingleZone, 1990s]
-
A.
zonedTo
Indicates that one entity is assigned or designated to fall within the jurisdiction, service area, or regulatory zone of another entity.
-
B.
zonedUse
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
-
C.
zoneBased
Indicates that the relationship or action is determined or constrained by specific geographic or logical zones.
-
D.
formerZone
Indicates that an entity was previously designated as a particular zone or area but no longer holds that status.
-
E.
usesZoning
Indicates that one entity applies or relies on a zoning scheme, classification, or regulations established or provided by another entity.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:31 p.m.