Triple
T35952705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode Cyrillic block |
E1039771
|
entity |
| Predicate | hasRelatedBlock |
P26441
|
FINISHED |
| Object | Cyrillic Supplement |
—
|
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: Cyrillic Supplement | Statement: [Unicode Cyrillic block, hasRelatedBlock, Cyrillic Supplement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelatedBlock Context triple: [Unicode Cyrillic block, hasRelatedBlock, Cyrillic Supplement]
-
A.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
-
B.
relatedBlock
chosen
Indicates that one block is associated with or connected to another block in some relevant way.
-
C.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
D.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
E.
hasRelatedGroup
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.