Triple
T37941943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Тимирязевская |
E946510
|
entity |
| Predicate | архитектор |
P160904
|
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: [Тимирязевская, архитектор, Н. Шумаков]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: архитектор Context triple: [Тимирязевская, архитектор, Н. Шумаков]
-
A.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
B.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
-
C.
architectProfession
chosen
Indicates that one entity has the profession or occupational role of an architect in relation to the other entity.
-
D.
supervisingArchitect
Indicates that one entity serves as the overseeing architect responsible for directing, reviewing, or approving the architectural work of another entity or project.
-
E.
architecturalSculptor
Indicates a relationship where a person serves as the sculptor responsible for the sculptural elements of an architectural work or structure.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.