Triple
T12790212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vova |
E305738
|
entity |
| Predicate | isNotUsedAs |
P106923
|
FINISHED |
| Object | formal legal given name in Russian documents |
—
|
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: formal legal given name in Russian documents | Statement: [Vova, isNotUsedAs, formal legal given name in Russian documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotUsedAs Context triple: [Vova, isNotUsedAs, formal legal given name in Russian documents]
-
A.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
B.
notUsedAt
Indicates that a particular entity is not utilized, applied, or active at a specified location, time, or context.
-
C.
notAutomaticallyUsedBy
Indicates that something is not used by another entity in an automatic or default manner and instead requires explicit action or configuration to be used.
-
D.
notUsedOnModel
Indicates that a particular item, component, or feature is not applied, installed, or utilized on the specified model.
-
E.
isAlsoUsedAs
Indicates that something serves an additional function or role beyond its primary one.
- F. None of above. chosen
Provenance (4 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6a61f48190972e241e70bc392c |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.