Triple
T37941971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Тимирязевская |
E946510
|
entity |
| Predicate | написание латиницей |
P163866
|
FINISHED |
| Object | Timiryazevskaya |
—
|
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: Timiryazevskaya | Statement: [Тимирязевская, написание латиницей, Timiryazevskaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: написание латиницей Context triple: [Тимирязевская, написание латиницей, Timiryazevskaya]
-
A.
usesLatinOrthography
chosen
Indicates that the subject’s written form is represented using the Latin (Roman) alphabet.
-
B.
isWrittenWith
Indicates that something is created or expressed using a particular writing tool, medium, or system.
-
C.
usesLatinAlphabetSince
Indicates that an entity has employed the Latin alphabet as its writing system starting from a specific point in time and continuing thereafter.
-
D.
writingSystem
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
E.
writingSystemDevelopedFor
Indicates that a particular writing system was created or adapted specifically to be used for a given language, community, or purpose.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.