Triple
T228394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish alphabet |
E4358
|
entity |
| Predicate | ISOBasicLatinSubset |
P1441
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Turkish alphabet, ISOBasicLatinSubset, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOBasicLatinSubset Context triple: [Turkish alphabet, ISOBasicLatinSubset, true]
-
A.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
B.
hasBasicLetters
chosen
Indicates that an entity contains or is composed of fundamental alphabetic characters, without additional symbols or diacritics.
-
C.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
-
D.
usesAlphabet
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
E.
usesCharacterSet
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d10ac248190a98dedabf5358668 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b5877588190af694d060377f027 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.