Triple
T34649490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Челкаш |
E889793
|
entity |
| Predicate | связанСПортом |
P179565
|
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 a general association or connection between one entity and another.
-
B.
relatedSport
Indicates that there is an association or connection between an entity and a particular sport.
-
C.
shipAssociatedWith
Indicates that there is a relevant connection or involvement between a ship and another entity, such as ownership, operation, registration, or functional association.
-
D.
associatedWithCitySports
Indicates a relationship where an entity has a connection or involvement with city-level sports activities, organizations, or events.
-
E.
ligadoA
Indicates that one entity is connected, linked, or otherwise associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.