Triple
T26773436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senatskaya Tower |
E670046
|
entity |
| Predicate | guardsBuilding |
P97703
|
FINISHED |
| Object | Kremlin Senate |
—
|
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: Kremlin Senate | Statement: [Senatskaya Tower, guardsBuilding, Kremlin Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardsBuilding Context triple: [Senatskaya Tower, guardsBuilding, Kremlin Senate]
-
A.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
-
B.
guard
chosen
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
C.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
D.
garrisonDuty
Indicates a relationship where an entity is assigned to stay and defend or guard a specific location as part of its military or protective duties.
-
E.
garrisonFunction
Indicates that an entity serves as a military garrison or base for another entity, providing housing, support, or operational facilities for its forces.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61930bca08190a3eb5073627bacce |
completed | May 2, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:03 a.m.