Triple
T35707549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrillic Pe |
E1031758
|
entity |
| Predicate | uppercaseUnicodeCodePoint |
P183843
|
FINISHED |
| Object | U+041F |
—
|
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: U+041F | Statement: [Cyrillic Pe, uppercaseUnicodeCodePoint, U+041F]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uppercaseUnicodeCodePoint Context triple: [Cyrillic Pe, uppercaseUnicodeCodePoint, U+041F]
-
A.
unicodeCodePoint
Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
-
B.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
C.
hasUnicodeCodePoint
Indicates that a character or symbol is associated with a specific numeric Unicode code point value.
-
D.
UnicodePlane
Indicates that a Unicode code point belongs to a specific Unicode plane (a contiguous range of code points grouped by plane number).
-
E.
UnicodeCodePointFinal
Indicates that one entity is the final (last) Unicode code point in a specified sequence or representation associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f76e0d393c8190b6303c64408736db |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.