Triple
T1284099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troitskaya Tower |
E27392
|
entity |
| Predicate | isAccessPointFor |
P26211
|
FINISHED |
| Object | official delegations |
—
|
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: official delegations | Statement: [Troitskaya Tower, isAccessPointFor, official delegations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessPointFor Context triple: [Troitskaya Tower, isAccessPointFor, official delegations]
-
A.
isMajorAccessPointFor
chosen
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
B.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
C.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
D.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
E.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b599ac819096fca9ada294d939 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.