Triple
T16990185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Литейный мост |
E412172
|
entity |
| Predicate | имеетКатегорию |
P15481
|
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.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
C.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
-
D.
hasRelatedCategory
Indicates that one category is associated with another category through a non-hierarchical, contextually relevant relationship.
-
E.
haveCategoryCode
Indicates that an entity is associated with a specific classification or category identified by a code.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27fbaa0819099f79fc74d211647 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.