Triple
T26073600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vladimirovna |
E657616
|
entity |
| Predicate | namingConventionRegion |
P159919
|
FINISHED |
| Object | former Soviet Union countries |
—
|
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: former Soviet Union countries | Statement: [Vladimirovna, namingConventionRegion, former Soviet Union countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namingConventionRegion Context triple: [Vladimirovna, namingConventionRegion, former Soviet Union countries]
-
A.
namingConventionRegion
chosen
Indicates that there is a specific regional or locale-based rule or pattern governing how something is named.
-
B.
namingConventionType
Indicates the specific style or set of rules used for naming entities or elements in a given context.
-
C.
namingConventionContext
Indicates the contextual rules or patterns that govern how something is named within a particular system or setting.
-
D.
namespaceConvention
Indicates the naming and structural rules that govern how namespaces are defined, organized, and referenced in a system.
-
E.
namingStructure
Indicates a relationship where one entity defines, organizes, or constrains the naming or label format used for another entity.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f606cde3608190a83c0f258d8b38b7 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 7:31 p.m.