Triple
T24743367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ипатьевский дом |
E618625
|
entity |
| Predicate | назван в честь |
P24365
|
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.
в его честь названы
Indicates that something has been named in honor of a particular person or entity.
-
B.
isNamedFor
chosen
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
C.
namedIn
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
D.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
E.
oftenNamedAfter
Indicates that one entity frequently receives its name from or in honor of 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:19 a.m.