Triple
T30877963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abramovich |
E786530
|
entity |
| Predicate | writtenAsInRussian |
P20560
|
FINISHED |
| Object | Абрамович |
—
|
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: Абрамович | Statement: [Abramovich, writtenAsInRussian, Абрамович]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenAsInRussian Context triple: [Abramovich, writtenAsInRussian, Абрамович]
-
A.
inscriptionTextRussian
Indicates that the associated inscription or written text is expressed in the Russian language.
-
B.
nameInRussian
chosen
Indicates that an entity is known or referred to by a specific name when expressed in the Russian language.
-
C.
hasRussianVersion
Indicates that something has a corresponding version or counterpart that is in the Russian language.
-
D.
currentNameInRussian
Indicates the current official name of an entity as expressed in the Russian language.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:48 p.m.