Triple
T32389684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Белая Троицкая церковь |
E827634
|
entity |
| Predicate | имеет колокольню |
P2495
|
FINISHED |
| Object | да (предположительно) |
—
|
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: да (предположительно) | Statement: [Белая Троицкая церковь, имеет колокольню, да (предположительно)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеет колокольню Context triple: [Белая Троицкая церковь, имеет колокольню, да (предположительно)]
-
A.
hasBellTower
chosen
Indicates that one entity (typically a building or structure) possesses or includes a bell tower as part of it.
-
B.
bellTowerStyle
Indicates the architectural style or design type of a bell tower in relation to a building or structure.
-
C.
hasClockTower
Indicates that one entity possesses or features a clock tower as part of its structure or property.
-
D.
hasBellChamber
Indicates that an entity possesses or includes a bell chamber as one of its structural or functional components.
-
E.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:52 a.m.