Triple
T24840310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Slavic Cyrillic |
E621595
|
entity |
| Predicate | sharesCharacterRepertoireWith |
P44216
|
FINISHED |
| Object | other Cyrillic alphabets |
—
|
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: other Cyrillic alphabets | Statement: [South Slavic Cyrillic, sharesCharacterRepertoireWith, other Cyrillic alphabets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCharacterRepertoireWith Context triple: [South Slavic Cyrillic, sharesCharacterRepertoireWith, other Cyrillic alphabets]
-
A.
sharesCharacterWith
chosen
Indicates that two entities have at least one character (such as a letter, symbol, or glyph) in common.
-
B.
sharesAppearanceTraitWith
Indicates that two entities possess at least one similar or matching visual or appearance-related characteristic.
-
C.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
-
D.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
E.
sharesSetsWith
Indicates that two entities have one or more sets in common, or participate in at least one identical set.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:18 a.m.