Triple
T7327893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sogdian alphabet |
E168919
|
entity |
| Predicate | numberOfLettersApproximate |
P7444
|
FINISHED |
| Object | 17–22 consonant signs |
—
|
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: 17–22 consonant signs | Statement: [Sogdian alphabet, numberOfLettersApproximate, 17–22 consonant signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLettersApproximate Context triple: [Sogdian alphabet, numberOfLettersApproximate, 17–22 consonant signs]
-
A.
hasApproximateNumberOfLetters
chosen
Indicates that an entity is associated with a number that roughly, but not exactly, corresponds to the count of letters it contains.
-
B.
hasNumberOfLetters
Indicates a relationship where an entity is associated with the count of letters it contains.
-
C.
hasLetterCount
Indicates that an entity is associated with a specific number representing how many letters it contains.
-
D.
lengthInWords
Indicates the number of words that make up the length of something, typically a text or expression.
-
E.
wordLength
Indicates that there is a relationship specifying the number of characters (length) in a given word.
- 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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0a879b88190bef0fb6cbae411ff |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:03 p.m.