Triple
T31789227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Зелёный мост |
E811414
|
entity |
| Predicate | включёнВ |
P1393
|
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.
ранееВходилоВ
Indicates that an entity previously belonged to, was part of, or was included within another entity, but is no longer included in it.
-
B.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
C.
используетсяС
Indicates that something is used together with or by means of another entity.
-
D.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
E.
aimedToInclude
Indicates that one entity intentionally sought to have another entity or element contained or incorporated within it.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac176b848190b9682ac08ea649e6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:38 p.m.