Triple
T16990172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Литейный мост |
E412172
|
entity |
| Predicate | типКонструкции |
P7599
|
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 the specific kind or category of building or structure associated with an entity.
-
B.
constructionType
chosen
Indicates the specific method or style by which something is built or constructed.
-
C.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
D.
typicalStructuralElement
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part of another entity.
-
E.
laterStructureType
Indicates that one structure is of a type that occurs or is instantiated later than another structure in a temporal or sequential sense.
- 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.