Triple
T34533083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markov |
E886592
|
entity |
| Predicate | usedInAlphabet |
P7160
|
FINISHED |
| Object | Cyrillic script |
—
|
NE NERFINISHED |
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 script | Statement: [Markov, usedInAlphabet, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAlphabet Context triple: [Markov, usedInAlphabet, Cyrillic script]
-
A.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
B.
usesLettersFrom
Indicates that one entity is formed or constructed using the letters that appear in another entity.
-
C.
previouslyUsedAlphabet
Indicates that an entity once employed a particular alphabet in the past, but no longer uses it as its current writing system.
-
D.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
E.
usesAlphabetResources
Indicates that an entity makes use of alphabet-related resources (such as letters, character sets, or alphabet-based tools) in performing an action or function.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 2:02 a.m.