Triple
T7456787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Uyghur alphabet |
E172144
|
entity |
| Predicate | hasCharacterSetSize |
P58060
|
FINISHED |
| Object | 22 letters (approximate) |
—
|
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: 22 letters (approximate) | Statement: [Old Uyghur alphabet, hasCharacterSetSize, 22 letters (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterSetSize Context triple: [Old Uyghur alphabet, hasCharacterSetSize, 22 letters (approximate)]
-
A.
characterSetSize
chosen
Indicates the total number of distinct characters contained in or allowed by a given character set.
-
B.
hasDistinctCharacterSet
Indicates that two compared items use different sets of characters, with no character set being a subset or duplicate of the other.
-
C.
usesCharacterSet
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
-
D.
hasNumberOfBasicCharacters
Indicates the quantity of basic (non-accented or fundamental) characters associated with an entity.
-
E.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3b0780881909e645160dd49eb57 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:15 p.m.