Triple
T34238170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha-Bits |
E878388
|
entity |
| Predicate | hasAlphabetCoverage |
P64709
|
FINISHED |
| Object | multiple letters of the alphabet |
—
|
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: multiple letters of the alphabet | Statement: [Alpha-Bits, hasAlphabetCoverage, multiple letters of the alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlphabetCoverage Context triple: [Alpha-Bits, hasAlphabetCoverage, multiple letters of the alphabet]
-
A.
characterCoverage
chosen
Indicates that one entity provides or includes sufficient representation or support for the characters (e.g., glyphs, symbols, or scripts) required or used by another entity.
-
B.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
C.
hasLatinAlphabetStandard
Indicates that there exists an established standard or convention for representing something using the Latin alphabet.
-
D.
hasCyrillicAlphabetForm
Indicates that an entity has a corresponding representation or form written in the Cyrillic alphabet.
-
E.
hasNumberOfBasicCharacters
Indicates the quantity of basic (non-accented or fundamental) characters associated with an entity.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 1, 2026, 1:56 a.m.