Triple
T8254926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherokee syllabary |
E193047
|
entity |
| Predicate | hasDistinctDigits |
P39011
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Cherokee syllabary, hasDistinctDigits, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDistinctDigits Context triple: [Cherokee syllabary, hasDistinctDigits, no]
-
A.
hasDistinctNumerals
chosen
Indicates that the numerals in the specified representation are all different from one another, with no digit repeated.
-
B.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
-
C.
hasDistinctLettersFor
Indicates that one entity is associated with another such that the letters used in the first are all different from (i.e., share no letters with) those used in the second.
-
D.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
E.
hasDistinctCharacterSet
Indicates that two compared items use different sets of characters, with no character set being a subset or duplicate of the other.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f8eccc8190b43204bf2f8defc1 |
completed | March 31, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.