Triple
T33223683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krasnoselskaya |
E850491
|
entity |
| Predicate | hasOriginalDecorationPreserved |
P153053
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Krasnoselskaya, hasOriginalDecorationPreserved, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalDecorationPreserved Context triple: [Krasnoselskaya, hasOriginalDecorationPreserved, yes]
-
A.
hasPreserved
chosen
Indicates that one entity has kept another entity intact, unchanged, or maintained in its original or functional state over time.
-
B.
hasOriginalPart
Indicates that an entity includes a component or segment that is part of its initial, original composition.
-
C.
hasOriginalComposition
Indicates that one entity is the initial or primary compositional source or makeup of another entity.
-
D.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
E.
hasOriginalPrefix
Indicates that an entity retains or is associated with its initial or primary prefix from which later forms or variants are derived.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:30 a.m.