Triple
T4233463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiatura |
E94634
|
entity |
| Predicate | writingSystemUsedLocally |
P26603
|
FINISHED |
| Object | Georgian script |
—
|
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: Georgian script | Statement: [Chiatura, writingSystemUsedLocally, Georgian script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemUsedLocally Context triple: [Chiatura, writingSystemUsedLocally, Georgian script]
-
A.
writingSystemUsedIn
chosen
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
-
B.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
C.
writingSystemUsedSince
Indicates that a particular writing system has been in use starting from a specified point in time or period.
-
D.
writingSystemLacks
Indicates that a particular writing system does not possess, include, or support a specified feature, element, or capability.
-
E.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e65720c819087c4022c774ff7c3 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.