Triple
T38377834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дворцовый мост |
E893673
|
entity |
| Predicate | имеетТипРазводки |
P192119
|
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.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
B.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
C.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
D.
conductorType
Indicates the type or category of conductor involved in the relationship or action (e.g., material, role, or functional class).
-
E.
conduitType
Indicates the specific kind or category of conduit through which something (such as energy, information, or material) is transmitted or carried.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:31 p.m.