Triple
T21389951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasily Bazhenov |
E527616
|
entity |
| Predicate | notableProjectCharacteristic |
P65006
|
FINISHED |
| Object | large-scale palace complexes |
—
|
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: large-scale palace complexes | Statement: [Vasily Bazhenov, notableProjectCharacteristic, large-scale palace complexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProjectCharacteristic Context triple: [Vasily Bazhenov, notableProjectCharacteristic, large-scale palace complexes]
-
A.
notableCollectionCharacteristic
Indicates that a collection is distinguished by a particular defining feature or quality that makes it notable.
-
B.
notableProjectFor
Indicates that a particular project is especially significant, prominent, or noteworthy for a given entity.
-
C.
projectCharacteristics
chosen
Indicates the defining features, qualities, or attributes that characterize a particular project.
-
D.
notableProjectType
Indicates the type or category of a project for which an entity is particularly well-known or notable.
-
E.
notableCriterion
Indicates that something is distinguished or recognized based on a particular standard, measure, or qualifying condition.
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0f8ae288190b43df9fe2841a822 |
completed | April 22, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:13 p.m.