Triple
T16990176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Литейный мост |
E412172
|
entity |
| Predicate | имеетЗначение |
P18302
|
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.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
B.
hasValue
chosen
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
hasCoreValue
Indicates that an entity possesses or is characterized by a fundamental guiding principle or core belief.
-
D.
valueDefinedBy
Indicates that the value of one entity is determined, specified, or constrained by another entity.
-
E.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
- 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.