Triple
T9045237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgian Extended |
E216738
|
entity |
| Predicate | containsUppercaseStyle |
P86058
|
FINISHED |
| Object | Mtavruli |
—
|
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: Mtavruli | Statement: [Georgian Extended, containsUppercaseStyle, Mtavruli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsUppercaseStyle Context triple: [Georgian Extended, containsUppercaseStyle, Mtavruli]
-
A.
hasUppercase
Indicates that an entity contains at least one uppercase (capital) letter.
-
B.
hasUppercaseForm
Indicates that one textual entity is the uppercase version or representation of another textual entity.
-
C.
isUppercasePreferred
Indicates that uppercase letters are favored or expected over other letter cases in a given context.
-
D.
hasUppercaseAndLowercase
Indicates that a string or text value contains at least one uppercase letter and at least one lowercase letter.
-
E.
hasUppercaseShapeDescription
Indicates that the description of a shape is written entirely in uppercase letters.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b148b188190814d64acae493634 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:09 p.m.