Triple
T16990180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Литейный мост |
E412172
|
entity |
| Predicate | имеетПокрытие |
P48754
|
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.
hasCoverings
Indicates that one entity possesses or is equipped with protective or enclosing layers, surfaces, or coverings provided by another entity.
-
B.
airCover
Indicates the provision of protective support from the air (such as aircraft or aerial defenses) to shield or assist another force, operation, or asset.
-
C.
surfaceCover
chosen
Indicates that one entity forms the material or layer that covers the outer surface of another entity.
-
D.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
E.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
- 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.