Triple
T30887330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Ring Road region |
E786801
|
entity |
| Predicate | transportPressure |
P196124
|
FINISHED |
| Object | peak-hour congestion |
—
|
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: peak-hour congestion | Statement: [Moscow Ring Road region, transportPressure, peak-hour congestion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportPressure Context triple: [Moscow Ring Road region, transportPressure, peak-hour congestion]
-
A.
typicalPressure
Indicates the usual or characteristic level of pressure typically associated with an entity, situation, or condition.
-
B.
navigatesPressureOf
Indicates a relationship where one entity manages, responds to, or operates under the influence or constraints of another entity’s pressure.
-
C.
pressureTransmission
Indicates that pressure applied at one point in a system is conveyed or propagated to another point within that system.
-
D.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
-
E.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
| PDg | Predicate description generation | batch_69fe08d1b3f881908eccb74cb0d246dc |
completed | May 8, 2026, 4:01 p.m. |
Created at: April 29, 2026, 8:49 p.m.